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 v2.8.1 - autoclosed #16

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 8, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
hashicorp/vault-action action minor v2.5.0 -> v2.8.1

Release Notes

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

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 - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone CET, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.6.0 chore(deps): update hashicorp/vault-action action to v2.7.0 Jun 21, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 7568840 to c17d708 Compare June 21, 2023 21:49
@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.7.0 chore(deps): update hashicorp/vault-action action to v2.7.1 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from c17d708 to 7a71c27 Compare July 3, 2023 18:27
@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.7.1 chore(deps): update hashicorp/vault-action action to v2.7.2 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 7a71c27 to 512c1cf Compare July 6, 2023 18:11
@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.7.2 chore(deps): update hashicorp/vault-action action to v2.7.3 Jul 13, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 512c1cf to f0ce16e Compare July 13, 2023 21:09
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from f0ce16e to 0d193f2 Compare July 27, 2023 15:42
@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.7.3 chore(deps): update hashicorp/vault-action action to v2.7.4 Oct 26, 2023
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 0d193f2 to 7f09e50 Compare October 26, 2023 15:44
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch 2 times, most recently from f75cf70 to 5bc9405 Compare December 6, 2023 15:32
@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.7.4 chore(deps): update hashicorp/vault-action action to v2.7.5 Jan 31, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 5bc9405 to 381e329 Compare January 31, 2024 00:48
@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.7.5 chore(deps): update hashicorp/vault-action action to v2.8.0 Feb 1, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 381e329 to 34ab568 Compare February 1, 2024 16:03
@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.8.0 chore(deps): update hashicorp/vault-action action to v2.8.1 Feb 15, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-vault-action-2.x branch from 34ab568 to 07ba445 Compare February 15, 2024 20:11
@renovate renovate bot changed the title chore(deps): update hashicorp/vault-action action to v2.8.1 chore(deps): update hashicorp/vault-action action to v2.8.1 - autoclosed Mar 27, 2024
@renovate renovate bot closed this Mar 27, 2024
@renovate renovate bot deleted the renovate/hashicorp-vault-action-2.x branch March 27, 2024 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
0 participants