Skip to content

breaking: the dependency actions/setup-node has been updated to a new major version (v6.4.0), which may include breaking changes. #major#44

Open
public-glueops-renovatebot[bot] wants to merge 2 commits into
mainfrom
renovate/actions-setup-node-6.x
Open

breaking: the dependency actions/setup-node has been updated to a new major version (v6.4.0), which may include breaking changes. #major#44
public-glueops-renovatebot[bot] wants to merge 2 commits into
mainfrom
renovate/actions-setup-node-6.x

Conversation

@public-glueops-renovatebot

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
actions/setup-node action major v4v6

Release Notes

actions/setup-node (actions/setup-node)

v6.4.0

Compare Source

What's Changed

Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v6...v6.4.0

v6.3.0

Compare Source

What's Changed

Enhancements:

When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node.

Dependency updates:
Bug fixes:

New Contributors

Full Changelog: actions/setup-node@v6...v6.3.0

v6.2.0

Compare Source

What's Changed

Documentation
Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v6...v6.2.0

v6.1.0

Compare Source

What's Changed

Enhancement:
Dependency updates:
Documentation update:

Full Changelog: actions/setup-node@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Breaking Changes

Dependency Upgrades

Full Changelog: actions/setup-node@v5...v6.0.0

v6

Compare Source

v5.0.0

Compare Source

What's Changed

Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless.
To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
  with:
    package-manager-cache: false

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Dependency Upgrades

New Contributors

Full Changelog: actions/setup-node@v4...v5.0.0

v5

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Mend Renovate.

yesterdaysrebel and others added 2 commits June 23, 2026 16:46
* feat: add OTEL backend service and wire extension to in-cluster API

* chore: add missing labeler config for CI

* feat: update otel-extension to version 0.1.1 and patch deployment configurations

* feat: update version to 0.1.1 and enhance backend service validation

* feat: improve service existence check for otel-extension-api in deployment script

* feat: enhance input validation with range checks for PORT and REQUEST_TIMEOUT_MS

* refactor: remove backend ownership from UI repo (transferred to argo-cd-extention-backend)

- Remove backend Deployment/Service/image publishing from argo-cd-ui-extention
- All backend source code removed (Dockerfile, package.json, src/)
- Release workflow now publishes only extension tarball (not Docker image)
- Updated all service references to argocd-extension-backend-api
- Removed EXTENSION_ENABLED toggle from all config layers
- helm-values.yaml, deploy.sh, and verify script updated to use external backend service
- Backend ownership now fully transferred to dedicated argo-cd-extention-backend repo

* feat(phase-2): add context-aware links component to UI extension
…ew major version (v6.4.0), which may include breaking changes. #major
@public-glueops-renovatebot

Copy link
Copy Markdown
Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant