Repository navigation
Tags
Tags
[NO-JIRA] Prepare 0.1.0 release (#703) Promotes the Unreleased changelog and sets VERSION.md to 0.1.0. After this PR is merged, automation creates releases/0.1.0 and immutable release-candidate/0.1.0-rc.1 refs. - [x] No public API or user-flow change Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
[NO-JIRA] Prepare 0.1.0 release (#703) Promotes the Unreleased changelog and sets VERSION.md to 0.1.0. After this PR is merged, automation creates releases/0.1.0 and immutable release-candidate/0.1.0-rc.1 refs. - [x] No public API or user-flow change Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
[NO-JIRA] Prepare 0.1.0 release (#703) Promotes the Unreleased changelog and sets VERSION.md to 0.1.0. After this PR is merged, automation creates releases/0.1.0 and immutable release-candidate/0.1.0-rc.1 refs. - [x] No public API or user-flow change Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
force reset version number (#646) ## Description Dealing with some growing pains in the release process. We want to manually delete previous 0.0.2 from 2 days ago and restart here.
fix(release) Confidential release handoff between repos (#641) Note: merge Arm-Debug/ASTL-confidential#80 after this PR ## Description Fix the release creation handoff between Arm-Debug/ASTL aand Arm-Debug/ASTL-confidential Key changes: - ASTL automatically creates release-candidate/VERSION after merging a preparation PR. - ASTL’s release workflow is reusable and accepts an exact candidate tag or SHA. - Stable releases verify the candidate tag, commit, changelog, version, and API policy. - ASTL-confidential calls ASTL’s workflow first, then builds the selected profile from the returned immutable SHA and version. - Removed confidential’s independent version calculation and obsolete VERSION.md bookkeeping. - Added workflow contract tests and updated release documentation/diagram. - ASTL VERSION.md remains 0.0.1. Fixes # (issue) ## Customer Impact Restores way to create a profile-specific (select which confidential projects to integrate) release in ASTL-Confidential based on a tagged release candidaate in ASTL. ## Performance Impact none ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) - [X] Testing, Verification, or CICD change ## Public API declaration Select exactly one. PR CI uses this declaration to enforce wrapper and changelog updates for behavioral changes that cannot be inferred from the public headers. Stable-release CI validates the cumulative SemVer requirement. - [X] No public API or user-flow change ## How Has This Been Tested? Validation passed: - ASTL: 39 tests, wrapper coverage, actionlint, yamllint, and diff checks. - ASTL-confidential: 12 release tests, actionlint, yamllint, and diff checks. ## Test Configuration macOS. ## Checklist - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules - [ ] I have checked my code and corrected any misspellings