8 Commits

Author	SHA1	Message	Date
Alexander Bayandin	2641ff3d1a	Use CI_ACCESS_TOKEN to create release PR (#5286) ... ## Problem If @github-actions creates release PR, the CI pipeline is not triggered (but we have `release-notify.yml` workflow that we expect to run on this event). I suspect this happened because @github-actions is not a repository member. Ref https://github.com/neondatabase/neon/pull/5283#issuecomment-1715209291 ## Summary of changes - Use `CI_ACCESS_TOKEN` to create a PR - Use `gh` instead of `thomaseizinger/create-pull-request` - Restrict permissions for GITHUB_TOKEN to `contents: write` only (required for `git push`)	2023-09-12 20:01:21 +01:00
Vadim Kharitonov	88b1ac48bd	Create Release PR at 7:00 UTC every Tuesday (#5213)	2023-09-06 13:17:52 +03:00
Alexander Bayandin	190c3ba610	Add tags for releases (#4524) ... ## Problem It's not a trivial task to find corresponding changes for a particular release (for example, for 3371 — 🤷) Ref: https://neondb.slack.com/archives/C04BLQ4LW7K/p1686761537607649?thread_ts=1686736854.174559&cid=C04BLQ4LW7K ## Summary of changes - Tag releases - Add a manual trigger for the release workflow	2023-06-16 14:17:37 +01:00
Vadim Kharitonov	e3cbcc2ea7	Revert "Add neondatabase/release team as a default reviewers for storage" ... This reverts commit daeaa767c4.	2023-03-27 14:10:18 +04:00
Vadim Kharitonov	daeaa767c4	Add neondatabase/release team as a default reviewers for storage ... releases	2023-03-13 13:40:15 +01:00
Vadim Kharitonov	a7d8bfa631	Fix create release PR	2023-01-31 14:36:04 +01:00
Vadim Kharitonov	ec0e641578	Create Release PR: review fixes	2023-01-30 16:15:22 +01:00
Vadim Kharitonov	5fc233964a	Create release PR	2023-01-30 12:44:48 +01:00