Repository navigation
chore(release): put the 0.4.0 identity ahead of main and describe the shipped cgm_cbio driver - #170
Closed
shroominic wants to merge 2 commits into
Closed
shroominic wants to merge 2 commits into
shroominic wants to merge 2 commits into
Conversation
…m_cbio driver The aggregates still declared 0.1.4+25 while main shipped 0.1.6+28, so an assembled 0.4.0 artifact would carry a version and build number below the released one. The release workflow also requires the tag to equal the pubspec version, so the train now records 0.4.0+29 (next build after main's +28). The cgm_cbio manifest and changelog still described an offline scaffold with no transport, authentication, or glucose support. Both now describe the delivered live driver, and the package version moves to 0.1.0 to match the other sensor packages.
The path dependency records the package version, so the 0.1.0 bump has to reach openhealth/pubspec.lock or make bootstrap fails under --enforce-lockfile.
Owner
Author
|
Carried by the GS1 consolidation in PR #209 (branch feature/cbio-gs1, head 3eca4f4). This PR is contained in the consolidated line; the merge that carries it is c85f827. Closing as subsumed by the consolidation - not as won't fix. The per-defect evidence stays in this thread, and the carrying commit above is where the change now lives. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the packaging-identity half of #157. The notice/inventory half stays on #165.
Defect
Both v0.4.0 aggregates declare
0.1.4+25inopenhealth/pubspec.yamlwhilemainhas shipped0.1.6+28. An assembled artifact would carry a version and build number below the released one, andrelease-android-beta.ymlrequires the tag to equal the pubspec version, so the train could not be taggedv0.4.0at all.packages/cgm_cbio/pubspec.yamland the package changelog still describe an offline, target-unverified scaffold with no transport, authentication, or glucose support. That stops being true once #136 lands the authenticated read session, and the root changelog repeated the same stale claim.Change
openhealth/pubspec.yaml->0.4.0+29(train version 0.4.0 to matchrelease/v0.4.0and its tag; build 29 is the next build aftermain's +28).packages/cgm_cbio/pubspec.yaml-> version0.1.0(matchescgm_libre2/cgm_yuwell_anytime) and a description that names the live driver and the injected vendor material.0.1.0section; the root changelog entry no longer claims the package has no transport or authentication.Not changed
Base
release/v0.4.0because the identity belongs to this release train; the aggregate merges this branch so the candidate carries the corrected identity.