search

the-hideout / tarkov-dev

The official site for tarkov.dev - A web app to track item prices, view trader barters, quests, maps, and much more!
https://tarkov.dev
MIT License
131 stars 47 forks source link

Bump the github-actions group with 4 updates #797

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 6 months ago

Bumps the github-actions group with 4 updates: github/branch-deploy, actions/setup-node, cloudflare/wrangler-action and GrantBirki/json-yaml-validate.

Updates github/branch-deploy from 8.1.2 to 8.2.0

Release notes

Sourced from github/branch-deploy's releases.

v8.2.0

What's Changed

Full Changelog: https://github.com/github/branch-deploy/compare/v8...v8.2.0

Commits


Updates actions/setup-node from 4.0.0 to 4.0.1

Release notes

Sourced from actions/setup-node's releases.

v4.0.1

What's Changed

New Contributors

Full Changelog: https://github.com/actions/setup-node/compare/v4...v4.0.1

Commits


Updates cloudflare/wrangler-action from 3.3.2 to 3.4.0

Release notes

Sourced from cloudflare/wrangler-action's releases.

v3.4.0

Minor Changes

  • #213 d13856dfc92816473ebf47f66e263a2668a97896 Thanks @​GrantBirki! - This change introduces three new GitHub Actions output variables. These variables are as follows:

    • command-output - contains the string results of stdout
    • command-stderr - contains the string results of stderr
    • deployment-url - contains the string results of the URL that was deployed (ex: https://<your_pages_site>.pages.dev)

    These output variables are intended to be used by more advanced workflows that require the output results or deployment url from Wrangler commands in subsequent workflow steps.

Patch Changes

  • #216 9aba9c34daabca23a88191a5fe1b81fa721c1f11 Thanks @​Cherry! - Fixes issues with semver comparison, where version parts were treated lexicographically instead of numerically.

    Bulk secret uploading was introduced in wrangler 3.4.0, and this action tries to check if the version used is greater than 3.4.0, and then if so, using the new bulk secret API which is faster. Due to a bug in the semver comparison, 3.19.0 was being considered less than 3.4.0, and then using an older and slower method for uploading secrets.

    Now the semver comparison is fixed, the faster bulk method is used for uploading secrets when available.

Changelog

Sourced from cloudflare/wrangler-action's changelog.

Changelog

3.4.0

Minor Changes

  • #213 d13856dfc92816473ebf47f66e263a2668a97896 Thanks @​GrantBirki! - This change introduces three new GitHub Actions output variables. These variables are as follows:

    • command-output - contains the string results of stdout
    • command-stderr - contains the string results of stderr
    • deployment-url - contains the string results of the URL that was deployed (ex: https://<your_pages_site>.pages.dev)

    These output variables are intended to be used by more advanced workflows that require the output results or deployment url from Wrangler commands in subsequent workflow steps.

Patch Changes

  • #216 9aba9c34daabca23a88191a5fe1b81fa721c1f11 Thanks @​Cherry! - Fixes issues with semver comparison, where version parts were treated lexicographically instead of numerically.

    Bulk secret uploading was introduced in wrangler 3.4.0, and this action tries to check if the version used is greater than 3.4.0, and then if so, using the new bulk secret API which is faster. Due to a bug in the semver comparison, 3.19.0 was being considered less than 3.4.0, and then using an older and slower method for uploading secrets.

    Now the semver comparison is fixed, the faster bulk method is used for uploading secrets when available.

3.3.2

Patch Changes

  • #171 76d614f Thanks @​1000hz! - Fixed issues that caused the action to fail if any secret or var values contained shell metacharacters.

  • #171 473d9cb Thanks @​1000hz! - Bumped DEFAULT_WRANGLER_VERSION to 3.13.2

3.3.1

Patch Changes

  • #193 a4509d5 Thanks @​1000hz! - Fixed the package manager not being inferred based on lockfile when the packageManager input isn't set.

3.3.0

Minor Changes

3.2.1

Patch Changes

  • #190 528687a Thanks @​1000hz! - Fixed action failure when no packageManager specified and no lockfile is found. The action now falls back to using npm.

3.2.0

... (truncated)

Commits


Updates GrantBirki/json-yaml-validate from 2.4.0 to 2.5.0

Release notes

Sourced from GrantBirki/json-yaml-validate's releases.

v2.5.0

What's Changed

Full Changelog: https://github.com/GrantBirki/json-yaml-validate/compare/v2.4.0...v2.5.0

Commits
  • 0be3fe3 Merge pull request #47 from GrantBirki/node-updates
  • 9b6cb7c node updates
  • 7c34098 Merge pull request #46 from GrantBirki/files-glob-match
  • 9b8ea63 coverage fixes
  • ab5e90c test
  • ebb8d2b update tests
  • fc0274e skip yaml files in the json validator if yamlAsJson === false
  • 42f2e19 update acceptance test and debugging
  • 703ebf8 use new exclude file
  • 6c5a67c add some tests files for the path acceptance tests
  • 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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will 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 minor version` will 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
github-actions[bot] commented 6 months ago

👋 Thanks for opening a pull request!

If you are new, please check out the trimmed down summary of our deployment process below:

  1. 👀 Observe the CI jobs and tests to ensure they are passing

  2. ✔️ Obtain an approval/review on this pull request

  3. 🚀 Deploy your pull request to the development environment with .deploy to development

  4. 🚀 Deploy your pull request to the production environment with .deploy

    If anything goes wrong, rollback with .deploy main

  5. 🎉 Merge!

Note: If you have a larger change and want to block deployments, you can run .lock --reason <reason> to lock all other deployments (remove with .unlock)

You can view the branch deploy usage guide for additional information

dependabot[bot] commented 6 months ago

Looks like these dependencies are updatable in another way, so this is no longer needed.