← Back to issue list

What's going on with charmcraft versions?

View original Github issue

Metadata

Project
charmcraft
Number
#365
Type
issue
State
closed
Author
heitorPB
Labels
—
Created
Updated
Closed

Current evaluation

Maintainers confirmed the snap versioning split was intentional: stable tracks numbered releases, while edge follows master using development git-hash versions; no code change was needed.

Resolution: closed not a bug

Reason: On 2021-08-09, facundobatista clarified that edge represents the evolving 1.2 line while stable contains patch releases such as 1.1.1. Earlier comments explained the same master-versus-stable distinction, and no resolving PR or commit was linked.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Hello. The `latest/edge` is 0.10.xx but the `latest/stable` is 1.0.0. The latest/edge was released more than a month after 1.0.0, but its version is <1.0.0? The `edge` is newer (the date is more recent) and older (the version number is lower) at the same time? ```bash $ snap info charmcraft name: charmcraft [...] snap-id: gcqfpVCOUvmDuYT0Dh5PjdeGypSEzNdV channels: latest/stable: 1.0.0 2021-04-30 (403) 10MB - latest/candidate: 1.0.0 2021-04-30 (403) 10MB - latest/beta: 1.0.0 2021-04-30 (403) 10MB - latest/edge: 0.10.0+126.g962eb50 2021-06-02 (435) 30MB classic installed: 1.0.0 (403) 10MB - ``` is this on purpose? I see GitHub Milestones for versions 0.11 and 0.12, but that should have happened before 1.0.0? This is confusing me, as the `pack` command is not the same on 1.0.0 and 0.10.0.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed not a bug Maintainers confirmed the snap versioning split was intentional: stable tracks numbered releases, while edge follows master using development git-hash versions; no code change was needed.
stealth/space-bunny-alpha — closed not a bug Maintainer confirmed the channel versions were intentional: stable carries numbered releases, while edge follows master with development git-hash versions. The concern was resolved without a code change.
qwen3.6-35b-a3b-mtp-q6 — — Maintainer clarified the stable/edge version mismatch was intentional after branching 1.0 to stable. Edge tracks master. Issue closed after explaining the strategy: stable gets numbered releases, edge tracks master with git hashes.
qwen/qwen3.6-35b-a3b — — Closed after clarifying the version mismatch was intentional during the 1.0 transition. Edge tracks master, stable receives specific releases. The channel strategy was explained, resolving the issue without code changes.
qwen/qwen3.6-35b-a3b — — The version mismatch was clarified as intentional. Stable tracks specific 1.x releases while edge reflects the master branch. Maintainers explained the snap channel structure and roadmap, resolving the confusion without code changes.
qwen3.6-35b-a3b-mtp-q6 — — Closed. Maintainers clarified the version mismatch was temporary. Stable tracks 1.x releases, edge reflects master. Resolution used roadmap alignment and channel strategy clarification, not code changes.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#4266 Charmcraft no longer builds from scratch using edge release of snapcraft snapcraft closed Closed as stale without a Snapcraft fix; Charmcraft PR #1146 proposed a workaround but was closed unmerged because it broke stable Snapcraft.
71%