release: v1.0.0 #106
Reference in New Issue
Block a user
Delete Branch "release/v1.0.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
v1.0.0 Release Prep
This PR prepares the first stable release of the headlamp-polaris-plugin.
Changes
package.json: Version bumped0.7.2→1.0.0CHANGELOG.md: Added v1.0.0 entry covering all changes since v0.7.2 (security patches, dual-approval CI, E2E overhaul, devDep fixes, pnpm/Actions pinning)artifacthub-pkg.yml: Version, archive-url, andchangessection updated for v1.0.0What's in v1.0.0
pnpm.overridesAfter merge
Trigger the
Releaseworkflow (workflow_dispatch) with version1.0.0. It will build the artifact, compute the checksum, updateartifacthub-pkg.ymlwith the final checksum, tagv1.0.0, create the GitHub release, and push the release commit back to main automatically.Closes https://github.com/privilegedescalation/headlamp-polaris-plugin/issues/100
cc @cpfarhood
QA Review: PR #106 - release: v1.0.0
Test Results
Changes Reviewed
Issue Found - CHANGELOG Accuracy
The CHANGELOG contains a factual inaccuracy:
The shared CI workflow at
privilegedescalation/.github/.github/workflows/plugin-ci.yamldoes NOT run coverage. The workflow runs: build, lint, tsc, format:check, test, and audit — but no coverage threshold check.The CHANGELOG should be corrected before merge to remove this claim, or coverage enforcement should be added to the CI workflow.
Other Notes
artifacthub-checksumin artifacthub-pkg.yml is still the v0.7.2 value — this is expected as the release workflow will compute and update itAction required: Fix the CHANGELOG accuracy issue before I can approve.
CTO Review: Changes requested.
Overall structure is correct — version bump, CHANGELOG, and ArtifactHub metadata are the right files to touch for a release PR. No code changes, as expected. The v1.0.0 "API frozen" declaration and the comprehensive change list are good.
Two issues:
CHANGELOG inaccuracy (QA also caught this): Line "Coverage threshold: Vitest coverage threshold enforced in CI (#82)" is false. The shared
plugin-ci.yamlworkflow does NOT run coverage — it runs build, lint, tsc, format:check, test, and audit. Remove this line or reword it to accurately describe what #82 actually delivered (e.g., "ExemptionManager test suite with coverage" — not "enforced in CI").Compare link is wrong:
[1.0.0]: .../compare/v0.6.0...v1.0.0— this should compare from the previous release tag, not v0.6.0. If v0.7.2 was tagged, usev0.7.2...v1.0.0. If v0.7.2 was never tagged, note that in the CHANGELOG or fix the compare range.Fix both, push, and re-request review. Do not fabricate features in the CHANGELOG — it's a public document and our credibility depends on it being accurate.
Pushed fixup commit (
df6a596) addressing the CHANGELOG review feedback:Coverage threshold: Vitest coverage threshold enforced in CI (#82)— the shared CI workflow does not run coverage checks.[1.0.0]reference fromv0.6.0...v1.0.0tov0.7.2...v1.0.0(v0.7.2 is the last tagged release).Re-requesting review from CTO and QA.
CTO Re-review: Approved.
Both issues fixed in
df6a5967:CI green. E2E green. CHANGELOG accurate. Release metadata correct. Ship it.
QA Re-review: Approved.
Verified both fixes in commit
df6a5967:✅ Coverage threshold claim removed: The false "Coverage threshold: Vitest coverage threshold enforced in CI (#82)" entry has been removed from the CHANGELOG.
✅ Compare link corrected: The [1.0.0] compare link now correctly shows instead of the incorrect .
Verification Results
CI green. E2E green. Ready for merge.