Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release-1.12.x): release 1.12.3 #115

Merged

Conversation

loki-gh-app[bot]
Copy link
Contributor

@loki-gh-app loki-gh-app bot commented Mar 11, 2024

🤖 I have created a release beep boop

1.12.3

1.12.3 (2024-03-18)

Features

  • add check template for GEL (5cc124c)
  • add secret to check template reuse (764eed8)
  • added build config needed for GEL (76f853d)
  • configurable changelog path (4b02163)
  • pass IMAGE_TAG as build arg (dc2bb7a)
  • publish artifacts to GCS bucket (f2b4793)
  • tag specific sha and set isLatest on release (#118) (24126d9)
  • try exposing IMAGE_TAG to docker build step (a618abe)
  • try using gcloud for docker auth (4b77ba8)

Bug Fixes

  • build job concat (b2fa59c)
  • move publish bucket stuff to correct place (a44e81d)
  • release version (c82545f)
  • remove unused secret from OSS workflow (c0962b5)

Merging this PR will release the artifacts of c82545f

@grafanabot
Copy link
Collaborator

This PR must be merged before a backport PR will be created.

1 similar comment
@grafanabot
Copy link
Collaborator

This PR must be merged before a backport PR will be created.

@loki-gh-app loki-gh-app bot force-pushed the release-please--branches--release-1.12.x branch 5 times, most recently from cb56f85 to 36c8603 Compare March 15, 2024 17:45
@loki-gh-app loki-gh-app bot changed the title chore(release-1.12.x): release 1.12.3 chore(release-1.12.x): release 1.12.0 Mar 18, 2024
@loki-gh-app loki-gh-app bot force-pushed the release-please--branches--release-1.12.x branch from 36c8603 to 5a038c3 Compare March 18, 2024 16:50
@loki-gh-app loki-gh-app bot changed the title chore(release-1.12.x): release 1.12.0 chore(release-1.12.x): release 1.12.3 Mar 18, 2024
@loki-gh-app loki-gh-app bot force-pushed the release-please--branches--release-1.12.x branch from 5a038c3 to 1fbfb05 Compare March 18, 2024 17:46
@loki-gh-app loki-gh-app bot force-pushed the release-please--branches--release-1.12.x branch from 1fbfb05 to ee76a3b Compare March 18, 2024 17:50
@trevorwhitney trevorwhitney merged commit 2612422 into release-1.12.x Mar 18, 2024
1 check passed
@trevorwhitney trevorwhitney deleted the release-please--branches--release-1.12.x branch March 18, 2024 17:51
@grafanabot
Copy link
Collaborator

The backport to main failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-115-to-main origin/main
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 261242214acc0de75c89902930501c8aec04cab2

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-115-to-main
# Create the PR body template
PR_BODY=$(gh pr view 115 --json body --template 'Backport 261242214acc0de75c89902930501c8aec04cab2 from #115{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "chore: [main] chore(release-1.12.x): release 1.12.3" --body-file - --label "autorelease: pending" --label "product-approved" --label "backport" --base main --milestone main --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-115-to-main

# Create a pull request where the `base` branch is `main` and the `compare`/`head` branch is `backport-115-to-main`.

# Remove the local backport branch
git switch main
git branch -D backport-115-to-main

@grafanabot
Copy link
Collaborator

@grafanabot
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants