Commit Graph
3 Commits
Author SHA1 Message Date
1grzyb1andClaude Opus 5.5 3580099c61 Fix(VIM-4350): Restrict What's New Claude workflow to maintainers and allowed files
Anyone could open a fork PR with the What's New title and inject a prompt
via a comment into a Claude run with repository write access.

- Run only for OWNER/MEMBER/COLLABORATOR comments, and verify the PR head is
  JetBrains/ideavim:whatsnew-tbr and the commenter has write access.
- Claude can only edit whatsnew-tbr.html and CHANGES.md and has no
  commit/push access; the push token is not persisted in .git/config.
- A separate step pushes the edits only if no other files changed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 11:49:16 +01:00
1grzyb1 5fd38b21b3 Improve release process
Our pipeline could mark issues on youtrack as fixed even if they were not in release branch.
Added single script for all pipelines to deremine which commits enetered given release so changelog, whats new and release itself are using exactly same logic
2026-10-09 10:13:18 +02:00
1grzyb1 0f7d95a8c9 Add workflow to update What's from PR 2026-06-30 13:07:33 +02:00