apm-agent-rum-js
apm-agent-rum-js copied to clipboard
chore: bump the github-actions group in /.github/workflows/run-test with 3 updates
Bumps the github-actions group in /.github/workflows/run-test with 3 updates: actions/setup-node, hashicorp/vault-action and actions/upload-artifact.
Updates actions/setup-node from 3 to 4
Release notes
Sourced from actions/setup-node's releases.
v4.0.0
What's Changed
In scope of this release we changed version of node runtime for action from node16 to node20 and updated dependencies in actions/setup-node#866
Besides, release contains such changes as:
- Upgrade actions/checkout to v4 by
@gmembre-zenikain actions/setup-node#868- Update actions/checkout for documentation and yaml by
@dmitry-shibanovin actions/setup-node#876New Contributors
@gmembre-zenikamade their first contribution in actions/setup-node#868Full Changelog: https://github.com/actions/setup-node/compare/v3...v4.0.0
v3.8.2
What's Changed
- Update semver by
@dmitry-shibanovin actions/setup-node#861- Update temp directory creation by
@nikolai-laevskiiin actions/setup-node#859- Bump
@babel/traversefrom 7.15.4 to 7.23.2 by@dependabotin actions/setup-node#870- Add notice about binaries not being updated yet by
@nikolai-laevskiiin actions/setup-node#872- Update toolkit cache and core by
@dmitry-shibanovand@seongwon-privatenotein actions/setup-node#875Full Changelog: https://github.com/actions/setup-node/compare/v3...v3.8.2
v3.8.1
What's Changed
In scope of this release, the filter was removed within the cache-save step by
@dmitry-shibanovin actions/setup-node#831. It is filtered and checked in the toolkit/cache library.Full Changelog: https://github.com/actions/setup-node/compare/v3...v3.8.1
v3.8.0
What's Changed
Bug fixes:
- Add check for existing paths by
@dmitry-shibanovin actions/setup-node#803- Resolve SymbolicLink by
@dmitry-shibanovin actions/setup-node#809- Change passing logic for cache input by
@dmitry-shibanovin actions/setup-node#816- Fix armv7 cache issue by
@louislamin actions/setup-node#794- Update check-dist workflow name by
@sinchangin actions/setup-node#710Feature implementations:
- feat: handling the case where "node" is used for tool-versions file. by
@xytisin actions/setup-node#812Documentation changes:
- Refer to semver package name in README.md by
@olleolleollein actions/setup-node#808Update dependencies:
- Update toolkit cache to fix zstd by
@dmitry-shibanovin actions/setup-node#804- Bump tough-cookie and
@azure/ms-rest-jsby@dependabotin actions/setup-node#802- Bump semver from 6.1.2 to 6.3.1 by
@dependabotin actions/setup-node#807
... (truncated)
Commits
Updates hashicorp/vault-action from 2.5.0 to 2.7.4
Release notes
Sourced from hashicorp/vault-action's releases.
v2.7.4
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
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
2.7.2 (July 6, 2023)
Bugs:
- Fix a regression that broke support for secrets in JSON format GH-473
v2.7.1
2.7.1 (July 3, 2023)
Bugs:
v2.7.0
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
2.6.0 (June 7, 2023)
Features:
- Add ability to set the
vault_tokenoutput 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-446Bugs:
- Handle undefined response in getSecrets error handler GH-431
Changelog
Sourced from hashicorp/vault-action's changelog.
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
2.7.3 (July 13, 2023)
Bugs:
- Revert to the handling of secrets in JSON format since v2.1.2 GH-478
2.7.2 (July 6, 2023)
Bugs:
- Fix a regression that broke support for secrets in JSON format GH-473
2.7.1 (July 3, 2023)
Bugs:
2.7.0 (June 21, 2023)
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
2.6.0 (June 7, 2023)
Features:
- Add ability to set the
vault_tokenoutput 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-446Bugs:
- Handle undefined response in getSecrets error handler GH-431
Commits
affa6f0Update to v2.7.4 (#499)4727f0bchore: update readme reference for readability (#497)86c7f83Revert "Update action.yml (#495)" (#496)375956aUpdate action.yml (#495)1328cd9Revert "Update Vault Action name in package.json (#493)" (#494)d4437eeUpdate Vault Action name in package.json (#493)a5f6c67Update README.md (#491)d9197ecImplemented wildcard selector (based on #238) (#488)cb841f2Update to v2.7.3 (#479)0010502fix secrets stored in JSON format, revert #473 (#478)- Additional commits viewable in compare view
Updates actions/upload-artifact from 3 to 4
Release notes
Sourced from actions/upload-artifact's releases.
v4.0.0
What's Changed
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
For more information, see the
@actions/artifactdocumentation.New Contributors
@vmjosephmade their first contribution in actions/upload-artifact#464Full Changelog: https://github.com/actions/upload-artifact/compare/v3...v4.0.0
v3.1.3
What's Changed
- chore(github): remove trailing whitespaces by
@ljmf00in actions/upload-artifact#313- Bump
@actions/artifactversion to v1.1.2 by@bethanyj28in actions/upload-artifact#436Full Changelog: https://github.com/actions/upload-artifact/compare/v3...v3.1.3
v3.1.2
- Update all
@actions/*NPM packages to their latest versions- #374- Update all dev dependencies to their most recent versions - #375
v3.1.1
- Update actions/core package to latest version to remove
set-outputdeprecation warning #351v3.1.0
What's Changed
- Bump
@actions/artifactto v1.1.0 (actions/upload-artifact#327)
- Adds checksum headers on artifact upload (actions/toolkit#1095) (actions/toolkit#1063)
Commits
c7d193fMerge pull request #466 from actions/v4-beta13131bblicensed cache4a6c273Merge branch 'main' into v4-betaf391bb9Merge pull request #465 from actions/robherley/v4-documentation9653d03Apply suggestions from code review875b630add limitations sectionecb2146add compression example5e7604ftrim some repeated infod6437d0naming1b56155s/v4-beta/v4/g- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions
Hi @v1v,
Is this PR related to these other two?
- https://github.com/elastic/apm-agent-rum-js/pull/1477
- https://github.com/elastic/apm-agent-rum-js/pull/1478
How should we proceed? Can things "break" if we merge them?
P.S. I'm asking out of curiosity, I just want to have more context and increase my knowledge on these topics
Looks like these dependencies are updatable in another way, so this is no longer needed.