Skip to content

fix(deps): update dependency metadata-connect to v1.2.2 - #682

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/metadata-connect-1.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/metadata-connect-1.x

Conversation

@renovate

@renovate renovate Bot commented Sep 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
metadata-connect 1.1.101.2.2 age confidence

Release Notes

chrisle/metadata-connect (metadata-connect)

v1.2.2

Compare Source

  • ci: CI comes from the shared connector-ci workflows

v1.2.1

Compare Source

  • ci: pull requests are tested the way main is

v1.2.0

Compare Source

  • feat: read the record label out of a track's tags

v1.1.11

Compare Source

  • ci: metadata-connect releases reach npm again instead of failing on every push

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 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.

@renovate
renovate Bot requested a review from thewrz as a code owner September 19, 2026 21:26
@renovate

renovate Bot commented Sep 19, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: bridge/package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EMISSINGTARGET
npm error Missing target in lock file: "node_modules/metadata-connect" is referenced by "node_modules/alphatheta-connect/node_modules/metadata-connect" but does not exist.
npm error To fix:
npm error 1. rm package-lock.json
npm error 2. npm install
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-19T21_26_33_564Z-debug-0.log

@coderabbitai

coderabbitai Bot commented Sep 19, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 0ed255cc-0584-462d-bf1e-56f39b7f2905

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
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.

0 participants