update(packaging): declare plugin compatible with ProperDocs

[Guts]

See: https://github.com/orgs/ProperDocs/discussions/33

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.74%. Comparing base (ce29ffc) to head (1a9e0da).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #431   +/-   ##
=======================================
  Coverage   83.74%   83.74%           
=======================================
  Files          11       11           
  Lines         769      769           
  Branches      129      129           
=======================================
  Hits          644      644           
  Misses         82       82           
  Partials       43       43           

Flag	Coverage Δ
unittests	83.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[miketheman]

Hey @Guts ! Curious about this one - since now both mkdocs and properdocs get installed as a result.

Thinking about it, would it make sense to even drop both as dependencies, since I'm guessing that folks installing this plugin would want one or the other, but probably not both?

[Guts]

@miketheman You're right but for now, it's the best solution I've found. It's a temporary solution, to let the ecosystem drama die down.

[miketheman]

@Guts I hear you completely. Not relying on either is a better overall solution in my head, but it's your choice of course.

The inclusion of both has prompted me to pin to the release prior to not get both installed and potentially have more drama.

[Guts]

As solution, you can do this :

1. fork this repo
2. create a branch like only-one-ssg
3. Remove the line you don't want in the pyproject.toml
4. On your website repo, tell pip to install through VCS pointing to your repo/branch

[miketheman]

Oh, it's fine - I wasn't asking for a complete solution, but thanks! I'm happy to sit and wait things out for now.

[Guts]

Let's see what will happen next. I hope things will calm down, although there will inevitably be some occasional flare-ups.

In the meanwhile, I'll continue to maintain and improve this plugin on my spare time.