📝 docs(release): prep v0.3.0 (E8 data-sources epic) - #35
Merged
Conversation
…se E8) - CHANGELOG: git-cliff [0.3.0] section (compare v0.2.2..v0.3.0) - README Marketplace badge + install/GHCR refs -> v0.3.0 - examples/install.yaml v0.2.1 -> v0.3.0 (fix pre-existing drift) - decisions.md: record D-022 (release v0.3.0 now, option A) with counterpoint - INBOX: convert release item to operator-only tail; drop stale v0.2.2 DECIDED block
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…ordination The Changelog verify gate requires CHANGELOG == plain 'git cliff' output ([Unreleased]). The [0.3.0] section is produced by the Changelog workflow's release job on tag push, not by hand. Revert the manual [0.3.0] edit; correct D-022 / INBOX to describe the auto changelog PR flow.
|
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.
Release-prep for v0.3.0 — decided D-022 → A via
/operator-inbox(2026-07-29)The E8 data-sources epic landed on
main(PRs #30–#33, integrated via #34): 2 new observe-only custom controllers (BackupList, PublicNetwork) + 38 observe-only example YAMLs, wired into provider startup. CI on the integrated tip is fully green. New additive controllers/CRDs ⇒ SemVer minor bump.What this PR does (reversible prep only)
v0.2.1→v0.3.0(fixes pre-existing drift; the v0.2.2 release bumped only README).git cliff→[Unreleased], so theChangelogverify gate passes). The versioned[0.3.0]section is not hand-written here — it is produced automatically by theChangelogworkflow'sreleasejob on the tag push.main.tag.yamlworkflow is broken — ref lackson.workflow_call):git tag v0.3.0 <merged-main-sha> && git push origin v0.3.0→ the tag push auto-opens a
changelog/v0.3.0PR with the release notes (merge it); it does not trigger publish.gh workflow run publish-provider-package.yml -f version=v0.3.0cosign verify ghcr.io/platformrelay/provider-gridscale:v0.3.0 --certificate-oidc-issuer https://token.actions.githubusercontent.com --certificate-identity-regexp 'https://github.com/PlatformRelay/provider-gridscale/.*'Not included (flagged)
openspec/changes/e8-data-sources/is untracked in the working tree (repo provenance, not in the shipped package). Left out to keep this PR clean — commit/archive separately if desired.