chore(release): bump version to 0.3.0 for semantic release#572
Merged
kcenon merged 1 commit intoMar 11, 2026
Merged
Conversation
Update project version from 0.1.0 to 0.3.0 in CMakeLists.txt and vcpkg.json to align with the semantic version tag being created for the vcpkg registry submission. This version is required by downstream ports (monitoring_system, logger_system) that declare a 0.3.0 dependency. Closes #570
Contributor
📊 Performance Benchmark ResultsPerformance Benchmark ReportNo benchmark data available. ℹ️ No baseline reference availableThis is the first benchmark run or baseline file is missing. |
kcenon
added a commit
that referenced
this pull request
Mar 11, 2026
…r docs Two pre-existing CI failures resolved: 1. OSV Vulnerability Scan: google/osv-scanner-action@v2 does not exist as a major-version tag. The repository only publishes specific patch versions (v2.3.3 is latest). Pinned both scan steps to v2.3.3. 2. Generate-Documentation: startup_failure caused by the reusable workflow (kcenon/common_system/.github/workflows/doxygen.yml) requiring `contents: write` permission (to deploy gh-pages) while the calling workflow had no explicit permissions block. Added `permissions: contents: write` at the workflow level so the called workflow can satisfy the permission requirement. Both failures have been occurring consistently since 2026-03-06 and are unrelated to the v0.3.0 version bump in #572.
6 tasks
kcenon
added a commit
that referenced
this pull request
Mar 11, 2026
…r docs (#573) Two pre-existing CI failures resolved: 1. OSV Vulnerability Scan: google/osv-scanner-action@v2 does not exist as a major-version tag. The repository only publishes specific patch versions (v2.3.3 is latest). Pinned both scan steps to v2.3.3. 2. Generate-Documentation: startup_failure caused by the reusable workflow (kcenon/common_system/.github/workflows/doxygen.yml) requiring `contents: write` permission (to deploy gh-pages) while the calling workflow had no explicit permissions block. Added `permissions: contents: write` at the workflow level so the called workflow can satisfy the permission requirement. Both failures have been occurring consistently since 2026-03-06 and are unrelated to the v0.3.0 version bump in #572.
This was referenced Mar 11, 2026
kcenon
added a commit
that referenced
this pull request
Apr 13, 2026
Update project version from 0.1.0 to 0.3.0 in CMakeLists.txt and vcpkg.json to align with the semantic version tag being created for the vcpkg registry submission. This version is required by downstream ports (monitoring_system, logger_system) that declare a 0.3.0 dependency. Closes #570
kcenon
added a commit
that referenced
this pull request
Apr 13, 2026
…r docs (#573) Two pre-existing CI failures resolved: 1. OSV Vulnerability Scan: google/osv-scanner-action@v2 does not exist as a major-version tag. The repository only publishes specific patch versions (v2.3.3 is latest). Pinned both scan steps to v2.3.3. 2. Generate-Documentation: startup_failure caused by the reusable workflow (kcenon/common_system/.github/workflows/doxygen.yml) requiring `contents: write` permission (to deploy gh-pages) while the calling workflow had no explicit permissions block. Added `permissions: contents: write` at the workflow level so the called workflow can satisfy the permission requirement. Both failures have been occurring consistently since 2026-03-06 and are unrelated to the v0.3.0 version bump in #572.
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.
What
Bump project version from 0.1.0 to 0.3.0 in
CMakeLists.txtandvcpkg.jsonto enable semantic version tag creation for vcpkg registry submission.Change Type
Why
Related Issues
Motivation
The vcpkg overlay port in downstream repositories (monitoring_system, logger_system) declares a
0.3.0dependency onkcenon-thread-system. The current codebase version (0.1.0) must be updated to match before creating thev0.3.0annotated git tag and GitHub Release.Additionally, the current
portfile.cmakeuses a raw commit SHA asREFand a placeholderSHA512 0, which blocks actual port installation and fails vcpkg PR review checklist c000005 (requires versioned archives, not branch HEADs or arbitrary commits).Who
Required Approvals
When
Urgency
Dependencies
Where
Files Changed
CMakeLists.txtVERSION 0.1.0.0→VERSION 0.3.0.0vcpkg.json"version": "0.1.0"→"version": "0.3.0"How
Implementation Details
Minimal, surgical change — only the two version fields are updated. No behavioral changes.
Post-merge Steps
After this PR is merged to main, the following steps will be performed:
git tag -a v0.3.0 -m "Release v0.3.0"git push origin v0.3.0gh release create v0.3.0 --generate-notesmonitoring_system/vcpkg-ports/kcenon-thread-system/portfile.cmakeREF and SHA512Testing Done
Breaking Changes
None — version string change only.