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(main): release get-vault-secrets 1.0.0 #423

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 27, 2024

🤖 I have created a release beep boop

1.0.0 (2024-10-17)

🎉 Features

🐛 Bug Fixes

  • get-vault-secrets: correct path to translate-secrets (#477) (62b49bb)
  • renovate: fix action versions, add more triggers (#249) (3b1e65f)

🤖 Continuous Integration

  • add workflow that lints shell scripts with ShellCheck (#147) (570898e)

🔧 Miscellaneous Chores

  • deps: update google-github-actions/auth action to v2.1.5 (#248) (a5d1613)
  • deps: update google-github-actions/auth action to v2.1.6 (#436) (a275eef)
  • deps: update hashicorp/vault-action action to v3 (#267) (553b76e)
  • Update action dependencies (#39) (b271a8b)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--get-vault-secrets branch 6 times, most recently from 0a2fee5 to d8bc58f Compare October 7, 2024 07:01
@github-actions github-actions bot force-pushed the release-please--branches--main--components--get-vault-secrets branch 6 times, most recently from 9949bc8 to f1e0d32 Compare October 15, 2024 05:58
@github-actions github-actions bot force-pushed the release-please--branches--main--components--get-vault-secrets branch 2 times, most recently from 8705d68 to 3cf0966 Compare October 16, 2024 11:59
@eloymg eloymg marked this pull request as ready for review October 16, 2024 12:59
@eloymg eloymg requested a review from a team as a code owner October 16, 2024 12:59
Copy link
Contributor

@dsotirakis dsotirakis left a comment

Choose a reason for hiding this comment

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

🚀

Copy link
Contributor

@dsotirakis dsotirakis left a comment

Choose a reason for hiding this comment

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

🚀

@dsotirakis
Copy link
Contributor

sorry for the double approve, got 500 error from github 😅
or just got too excited 😁

@eloymg eloymg enabled auto-merge October 16, 2024 15:24
@github-actions github-actions bot force-pushed the release-please--branches--main--components--get-vault-secrets branch 2 times, most recently from 24f736e to 7b23bc4 Compare October 16, 2024 16:44
@iainlane
Copy link
Member

I think if we merge #479 and then rebase this we should get CI results which let this be merged.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--get-vault-secrets branch from 7b23bc4 to 2cd0d92 Compare October 17, 2024 05:59
@github-actions github-actions bot force-pushed the release-please--branches--main--components--get-vault-secrets branch from 2cd0d92 to 5260293 Compare October 17, 2024 08:23
@eloymg eloymg force-pushed the release-please--branches--main--components--get-vault-secrets branch from 5260293 to 72eaf52 Compare October 17, 2024 08:34
@eloymg eloymg added this pull request to the merge queue Oct 17, 2024
Merged via the queue into main with commit cb307dc Oct 17, 2024
11 checks passed
@eloymg eloymg deleted the release-please--branches--main--components--get-vault-secrets branch October 17, 2024 08:37
Copy link
Contributor Author

🤖 Created releases:

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.

3 participants