Skip to content

chore: Cherry-picked changes from upstream #127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
github-actions wants to merge 2 commits into from
Closed

chore: Cherry-picked changes from upstream #127

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4fc86a9
Add automated release workflows for latest branch sync and version ta…
github-actions[bot] Feb 19, 2026
52cef3a
Merge branch 'main' into auto-cherry-pick
Raj-StepSecurity Apr 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,8 +144,19 @@ To build, pack and run all tests:

<br>

## Release Process
When a new CMake or Ninja version is merged to the main branch, a release should be performed to make it available to users via the `@latest` branch reference and version tags.

See [RELEASE_PROCESS.md](./RELEASE_PROCESS.md) for detailed instructions.

**Quick summary:**
- **Automated**: The `auto-release.yml` workflow automatically creates releases when CMake version PRs are merged
- **Manual**: Use the "Sync latest branch and create release tag" workflow in GitHub Actions to manually trigger a release

<br>

# License
All the content in this repository is licensed under the [MIT License](LICENSE).

Copyright (c) 2020-2021-2022-2023-2024 Luca Cappa
Copyright (c) 2025 Step Security
Copyright (c) 2025 Step Security
Loading