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(deps): update hashicorp/vault-action action to v3 #130

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2024

This PR contains the following updates:

Package Type Update Change
hashicorp/vault-action action major v2.5.0 -> v3.0.0

Release Notes

hashicorp/vault-action (hashicorp/vault-action)

v3.0.0

Compare Source

3.0.0 (February 15, 2024)

Improvements:

  • Bump node runtime from node16 to node20 GH-528

v2.8.1

Compare Source

2.8.1 (February 15, 2024)

Bugs:

  • Revert GH-509 which made a backwards incompatible bump of the node runtime from node16 to node20 GH-527

v2.8.0

Compare Source

2.8.0 (February 1, 2024)

Features:

  • Add ignoreNotFound input (default: false) to prevent the action from failing when a secret does not exist GH-518

Improvements:

v2.7.5

Compare Source

2.7.5 (January 30, 2024)

Improvements:

  • Bump node runtime from node16 to node20 GH-509
  • Bump got from 11.8.5 to 11.8.6 GH-492

v2.7.4

Compare Source

2.7.4 (October 26, 2023)

Features:

  • Add ability to specify a wildcard for the key name to get all keys in the path GH-488

v2.7.3

Compare Source

2.7.3 (July 13, 2023)

Bugs:

  • Revert to the handling of secrets in JSON format since v2.1.2 GH-478

v2.7.2

Compare Source

2.7.2 (July 6, 2023)

Bugs:

  • Fix a regression that broke support for secrets in JSON format GH-473

v2.7.1

Compare Source

2.7.1 (July 3, 2023)

Bugs:

  • Revert GH-466 which caused a regression in secrets stored as JSON strings GH-471

v2.7.0

Compare Source

Bugs:

  • Fix a regression that broke support for secrets in JSON format GH-466

Improvements:

  • Fix a warning about outputToken being an unexpected input GH-461

v2.6.0

Compare Source

2.6.0 (June 7, 2023)

Features:

  • Add ability to set the vault_token output to contain the Vault token after authentication GH-441
  • Add support for userpass and ldap authentication methods GH-440
  • Define an output, errorMessage, for vault-action's error messages so subsequent steps can read the errors GH-446

Bugs:

  • Handle undefined response in getSecrets error handler GH-431

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@nahsi nahsi closed this Sep 4, 2024
Copy link
Contributor Author

renovate bot commented Sep 4, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/hashicorp-vault-action-3.x branch September 4, 2024 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant