ci: update release actions and use published design tokens - #163
Merged
Conversation
Bumps the actions group with 3 updates: [anchore/sbom-action](https://github.com/anchore/sbom-action), [python-semantic-release/python-semantic-release](https://github.com/python-semantic-release/python-semantic-release) and [python-semantic-release/publish-action](https://github.com/python-semantic-release/publish-action). Updates `anchore/sbom-action` from 0.24.0 to 0.24.2 - [Release notes](https://github.com/anchore/sbom-action/releases) - [Changelog](https://github.com/anchore/sbom-action/blob/main/RELEASE.md) - [Commits](anchore/sbom-action@e22c389...3ad7283) Updates `python-semantic-release/python-semantic-release` from 10.6.1 to 10.6.2 - [Release notes](https://github.com/python-semantic-release/python-semantic-release/releases) - [Changelog](https://github.com/python-semantic-release/python-semantic-release/blob/master/CHANGELOG.rst) - [Commits](python-semantic-release/python-semantic-release@39dd205...9a026e9) Updates `python-semantic-release/publish-action` from 10.6.1 to 10.6.2 - [Release notes](https://github.com/python-semantic-release/publish-action/releases) - [Changelog](https://github.com/python-semantic-release/publish-action/blob/main/releaserc.toml) - [Commits](python-semantic-release/publish-action@5a5718c...6d89e2d) --- updated-dependencies: - dependency-name: anchore/sbom-action dependency-version: 0.24.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions - dependency-name: python-semantic-release/python-semantic-release dependency-version: 10.6.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions - dependency-name: python-semantic-release/publish-action dependency-version: 10.6.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
abrichr
changed the title
This was referenced Sep 10, 2026
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
1 participant
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.
Dependency PRs can't read the private Web repository with their scoped GitHub token. The token check now compares Desktop's vendored files with the exact public copies at
openadapt.ai/styles/tokens.jsonandtokens.css. It still fails on changed bytes or a failed fetch. The authenticated write command continues to import from the canonical repository.The release workflows use python-semantic-release and publish-action 10.6.2, plus sbom-action 0.24.2. Their pinned commits match the upstream tags, and the release contract assertions now name 10.6.2. The SBOM action also moves its default Syft version from 1.42.3 to 1.51.1 and pins the installer to that release. Its CycloneDX 1.7 output remains accepted by the existing validator. Publication remains manual.
Validation: 1,089 Python tests passed (16 skipped), 122 UI tests passed, the frontend build and Ruff passed, and the public token bytes matched both vendored SHA-256 values.