Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 21, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/git 9.0.0 -> 9.0.1 age confidence
@semantic-release/github 7.2.0 -> 7.2.3 age confidence
@semantic-release/npm 7.0.6 -> 7.1.3 age confidence
@semantic-release/release-notes-generator 9.0.1 -> 9.0.3 age confidence

Release Notes

semantic-release/git (@​semantic-release/git)

v9.0.1

Compare Source

Bug Fixes
semantic-release/github (@​semantic-release/github)

v7.2.3

Compare Source

Bug Fixes

v7.2.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v10 (1a28625)

v7.2.1

Compare Source

Bug Fixes
  • allow proxy to be false and fallback an empty string (#​356) (bea917f)
semantic-release/npm (@​semantic-release/npm)

v7.1.3

Compare Source

Bug Fixes
  • use NPM_CONFIG_USERCONFIG in get-registry to match auth (#​362) (13200ca)

v7.1.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v10 (80fde1e)

v7.1.1

Compare Source

Bug Fixes
  • deps: update dependency normalize-url to v6 (97ca719)

v7.1.0

Compare Source

Features

v7.0.10

Compare Source

Bug Fixes

v7.0.9

Compare Source

Bug Fixes

v7.0.8

Compare Source

Bug Fixes

v7.0.7

Compare Source

Bug Fixes
semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v9.0.3

Compare Source

Bug Fixes
  • deps: update dependency get-stream to v6 (d8abb62)

v9.0.2

Compare Source

Bug Fixes
  • deps: update dependency into-stream to v6 (9f33802)

Configuration

📅 Schedule: 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.

👻 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from e8a73a7 to af5207e Compare March 3, 2025 12:53
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 3 times, most recently from a6fff9f to a87586f Compare March 17, 2025 17:05
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 966885b to 2cccf9e Compare April 8, 2025 11:01
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 2cccf9e to 6aed33c Compare April 24, 2025 09:16
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 6aed33c to 82a1edc Compare May 19, 2025 16:45
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from da18b97 to bc0d1f9 Compare June 4, 2025 06:39
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from bc0d1f9 to 16abc82 Compare June 22, 2025 14:04
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 16abc82 to a96b45d Compare July 2, 2025 16:06
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from f6c4abf to d966587 Compare August 13, 2025 13:49
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from d966587 to 18aa02f Compare August 19, 2025 14:42
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 18aa02f to 6b68971 Compare August 31, 2025 09:59
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 6b68971 to eececfe Compare September 25, 2025 20:49
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