Skip to content

fix: sync v2.0.0 release and use PR for publish version bumps#22

Merged
carlos-alm merged 1 commit intomainfrom
fix/sync-v2-and-publish-workflow
Feb 22, 2026
Merged

fix: sync v2.0.0 release and use PR for publish version bumps#22
carlos-alm merged 1 commit intomainfrom
fix/sync-v2-and-publish-workflow

Conversation

@carlos-alm
Copy link
Contributor

Summary

  • Sync v2.0.0: Bumps package.json from 1.4.0 → 2.0.0 (including optionalDependencies) and renames the CHANGELOG header from 1.5.0 → 2.0.0 to match what was actually published on npm. The CI version bump commit couldn't be pushed to main due to branch protection.
  • Fix publish workflow: Replaces the direct git push origin main with creating a release/vX.Y.Z branch and opening a PR via gh pr create. This respects branch protection rules that require PRs and status checks. Also adds pull-requests: write permission to the publish job.

Test plan

  • Verify package.json version is 2.0.0 and optionalDependencies reference 2.0.0
  • Verify CHANGELOG heading reads 2.0.0 instead of 1.5.0
  • On next publish run, confirm the workflow creates a release/vX.Y.Z PR instead of pushing directly to main

- Bump package.json from 1.4.0 to 2.0.0 to match what was published
  on npm (the CI version bump commit could not be pushed due to
  branch protection)
- Update optionalDependencies to reference 2.0.0 platform packages
- Rename CHANGELOG 1.5.0 header to 2.0.0 to match the actual release
- Replace direct git push to main in publish workflow with creating a
  release/vX.Y.Z branch and opening a PR via gh, which respects
  branch protection rules requiring PRs and status checks
- Add pull-requests: write permission to the publish job
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 22, 2026

Greptile Summary

Syncs the repository state with the published v2.0.0 npm release and fixes the publish workflow to respect branch protection rules.

  • Version sync: Updates package.json and CHANGELOG header from 1.4.0/1.5.0 → 2.0.0 to match what was already published on npm
  • Platform packages: Updates all four @optave/codegraph-* platform-specific optionalDependencies to 2.0.0 (handled automatically by scripts/sync-native-versions.js via the npm version lifecycle hook)
  • Workflow fix: Replaces direct git push origin main with a PR-based approach (release/vX.Y.Z branch + gh pr create) to comply with branch protection requiring PRs and status checks
  • Permissions: Adds pull-requests: write to the publish job for PR creation
  • Tag handling: Preserves tag creation logic with duplicate detection

Confidence Score: 5/5

  • This PR is safe to merge with no risk
  • Clean sync commit with well-scoped changes: version number updates are consistent across all files (including auto-synced platform dependencies), the workflow fix properly addresses branch protection with standard GitHub Actions patterns, and all changes align with the stated purpose of syncing the v2.0.0 release
  • No files require special attention

Important Files Changed

Filename Overview
.github/workflows/publish.yml Replaces direct push to main with PR-based version bump workflow to respect branch protection rules
package.json Syncs version from 1.4.0 → 2.0.0 and updates platform-specific optionalDependencies to match
CHANGELOG.md Corrects version header from 1.5.0 → 2.0.0 to match published npm version

Last reviewed commit: 3aab964

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 files reviewed, no comments

Edit Code Review Agent Settings | Greptile

@carlos-alm carlos-alm merged commit 5dbec8e into main Feb 22, 2026
15 checks passed
@carlos-alm carlos-alm deleted the fix/sync-v2-and-publish-workflow branch February 22, 2026 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant