JC Grünhage aedeb37220 fix(ci): put the BUILD_TAG of the upcoming release into RC PR artifacts (#11304) ...

## Problem
#11061 changed how artifacts for releases are built, by
reusing/retagging the artifacts from release PRs. This resulted in the
BUILD_TAG that's baked into the images to not be as expected.
Context: https://neondb.slack.com/archives/C08JBTT3R1Q/p1742333300129069

## Summary of changes
Set BUILD_TAG to the release tag of the upcoming release when running
inside release PRs.

2025-03-19 09:34:28 +00:00

..

actions

Fix artifact name for build with sanitizers (#11066)

2025-03-03 18:00:53 +00:00

ISSUE_TEMPLATE

[infra/notes] impr: add issue types to issue templates (#10018)

2025-01-31 06:29:06 +00:00

scripts

impr(ci): use ghcr.io as the default container registry (#11210)

2025-03-18 11:30:49 +00:00

workflows

fix(ci): put the BUILD_TAG of the upcoming release into RC PR artifacts (#11304)

2025-03-19 09:34:28 +00:00

actionlint.yml

fix(ci): use <!subteam^ID> syntax for pinging groups on slack (#11135)

2025-03-10 13:27:23 +00:00

file-filters.yaml

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

pull_request_template.md

Remove checklist from the PR template (#9702)

2024-11-11 17:01:02 +00:00