docs: improve versioning logic
Metadata
Current evaluation
Merged after approval and passing CI checks. Updated documentation versioning logic to label the latest release as Charmcraft dev documentation. Integrated with minimal changes ahead of the 4.3 tag.
Suggested action: —
No scores available.
Issue body
No versions but 'latest' should be labeled 'Charmcraft dev documentation'.
---
- [X] I've followed the [contribution guidelines](https://github.com/canonical/charmcraft/blob/main/CONTRIBUTING.md).
- [X] I've signed the [CLA](http://www.ubuntu.com/legal/contributors/).
- [ ] I've successfully run `make lint && make test`.
- [ ] I've added or updated any relevant documentation.
- [ ] In documents I changed, I [added a meta description](https://canonical-starflow.readthedocs-hosted.com/how-to/add-a-page-meta-description/) if one was missing.
- [ ] I've updated the relevant release notes.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged after approval and passing CI checks. Updated documentation versioning logic to label the latest release as Charmcraft dev documentation. Integrated with minimal changes ahead of the 4.3 tag. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged to update documentation versioning logic. The 'latest' version now displays as 'Charmcraft dev documentation' when no other versions exist. Integrated ahead of v4.3 to fix title text before proxy updates. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2728 docs: add 4.3 release notes | charmcraft | merged | Merged documentation update adding release notes for Charmcraft 4.3.0 and placeholder notes for 4.4. Approved by one reviewer and passed all CI checks before integration. | |
| #2589 docs: add Charmcraft 4.2 release notes | charmcraft | merged | Merged pull request adding Charmcraft 4.2 release notes. The update adds 113 lines across two documentation files. Changes were reviewed, approved, and successfully integrated into the main branch. | |
| #2483 docs: add Charmcraft 4.1 release notes | charmcraft | merged | Merged documentation adding Charmcraft 4.1 release notes. The page was intentionally left unindexed pending a separate bases policy page. Approved by two reviewers and passed CI, with a persistent non-blocking type-check warning noted. | |
| #2306 docs: release notes for Charmcraft 4.0 | charmcraft | merged | Merged PR adding release notes for Charmcraft 4.0. Approved by three reviewers. CI passed with non-blocking type checking warnings. Changes: +186/-5 lines across 4 files. | |
| #2801 docs: add Charmcraft 4.4 release notes | charmcraft | merged | Added Charmcraft 4.4 release notes. Merged after approval and passing CI checks. Updates four files (+188/-4 lines) to address CHARMCRAFT-711. | |
| #2202 docs: add initial 3.5 release notes | charmcraft | merged | Merged after approval. Added initial release notes for Charmcraft 3.5, incorporating new features and deprecation notes from 3.4. Integration completed following successful CI checks. | |
| #2358 docs: release Charmraft 3.5.2 | charmcraft | merged | Merged to publish Charmcraft 3.5.2. Changes update release notes and cherry-pick fixes from main. Approved by two reviewers and merged after passing the majority of CI checks, with a few failing tests disregarded. | |
| #2832 docs: fix version string for 4.x | charmcraft | merged | Merged. Updated documentation to correctly display major and minor version strings for local, PR, and branch builds, reserving 'dev' for the latest branch. Approved by one reviewer with all CI checks passing. | |
| #2300 docs: update "manage configurations" | charmcraft | merged | Merged after two reviewers approved. Updated Charmcraft documentation links and renamed the section to Manage the app configuration per feedback. All CI checks passed and changes were integrated. | |
| #2496 docs: add Charmcraft 4.1 release notes | charmcraft | closed | Rejected and closed without merging. Reviewer flagged that the proposed release notes contained irrelevant details, duplicated existing documentation, and included an incorrect claim about experimental bases. No changes were applied. |