Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency @semantic-release/gitlab to v9 #148

Merged
merged 1 commit into from
May 16, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 21, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/gitlab ^7.0.4 -> ^9.0.0 age adoption passing confidence

Release Notes

semantic-release/gitlab

v9.3.0

Compare Source

Features

v9.2.1

Compare Source

Bug Fixes

v9.2.0

Compare Source

Features

v9.1.3

Compare Source

Bug Fixes

v9.1.2

Compare Source

Bug Fixes
  • verify: gracefully handle options without validator (#​364) (24a8fb9)

v9.1.1

Compare Source

Bug Fixes

v9.1.0

Compare Source

Features

v9.0.0

Compare Source

Features
BREAKING CHANGES
  • Issues will be created or are commented by default . Set the failComment or failTitle option to false to disable this behavior.

Co-authored-by: Jonas Schubert jonas.schubert@siemens.com
Co-authored-by: Florian Greinacher florian@greinacher.de

v8.1.0

Compare Source

Features

v8.0.2

Compare Source

Bug Fixes
  • success-comment: add missing dot and line break to improve readability (#​353) (87c0246), closes #​351

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

Features
  • comment on issues and merge requests resolved by current release (#​340) (42c31ac)
BREAKING CHANGES
  • By default all related issues and MRs are commented. Set the successComment option to false to disable this behavior.

Configuration

📅 Schedule: 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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d84ca10 to 0e4ebb7 Compare March 28, 2022 03:37
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0e4ebb7 to 9f40460 Compare April 4, 2022 06:49
@travi
Copy link
Member

travi commented Apr 6, 2022

@fgreinacher what thoughts would you have about getting this merged? it would expose the new version to consumers of this config. would you consider the v8 upgrade to be breaking for this config (i think i lean toward yes, but am interested in your thoughts)?

@renovate renovate bot changed the title fix(deps): update dependency @semantic-release/gitlab to v8 fix(deps): update dependency @semantic-release/gitlab to v9 Apr 9, 2022
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9f40460 to 210fd5f Compare April 9, 2022 18:02
@fgreinacher
Copy link
Contributor

@fgreinacher what thoughts would you have about getting this merged? it would expose the new version to consumers of this config. would you consider the v8 upgrade to be breaking for this config (i think i lean toward yes, but am interested in your thoughts)?

@travi I just merged one more breaking change. I’d suggest we wait a week or so just to make sure there is some adoption before including it here.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 210fd5f to 12b4090 Compare April 11, 2022 04:27
@travi
Copy link
Member

travi commented Apr 11, 2022

I’d suggest we wait a week or so just to make sure there is some adoption before including it here.

thats fair. i normally like to make new features available as early as we can, but i mainly want to make sure we dont lose track of this as things continue forward. sounds like you've got a handle on it, so i'm good with that

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 12b4090 to 76de3c2 Compare April 18, 2022 07:44
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 76de3c2 to 2907cdc Compare May 2, 2022 04:09
Copy link
Contributor

@fgreinacher fgreinacher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@travi Let’s go for this now 😀

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2907cdc to 86680b2 Compare May 9, 2022 05:31
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 86680b2 to 8e08388 Compare May 16, 2022 06:10
@travi
Copy link
Member

travi commented May 16, 2022

sorry for missing your follow up message, @fgreinacher. also just realized that the gitlab team didnt have proper permissions on this repo, so i've fixed that. i'll let you merge this one since you will be most able to respond to anything that comes up as a result

@fgreinacher
Copy link
Contributor

@travi No worries and thanks for providing permissions!

@fgreinacher fgreinacher merged commit 476fe8d into master May 16, 2022
@fgreinacher fgreinacher deleted the renovate/major-semantic-release-monorepo branch May 16, 2022 16:39
@github-actions
Copy link

🎉 This PR is included in version 10.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants