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

[Potentially Breaking] updated tlvince-semantic-release-bundle-bump-bot to version 1.0.0 #1

Closed
wants to merge 1 commit into from

Conversation

tlvince
Copy link
Owner

@tlvince tlvince commented Sep 22, 2015

Dear tlvince-semantic-release-bundle-bump-bot maintainer,

tlvince-semantic-release-bundle-bump-bot, one of your dependencies, just released a new major -- 1.0.0.
I'm just a bot and unfortunately I can't yet know if that breaks tlvince-semantic-release-bundle-bump-bot as well.

Generally if a breaking change appears in a component there are two options:

  1. A new version of an accompanying component makes up for the breaking change, so that if they're used together the public API doesn't break.
  2. This is an actual breaking change for tlvince-semantic-release-bundle-bump-bot as well.

Please try and figure that out with your amazing human brain.

In case of the former please wait for the accompanying component to release its new version and manually update both versions in one commit. You can close this PR.

In case of the latter please document the breaking change by adding another empty commit that declares the breaking change and includes migration instructions.

This could look something like this:

git commit --allow-empty

The editor opens.

docs(changelog): declare breaking change

BREAKING CHANGE: Feature xyz broke in version x.y.z of hoodie-whatever.

Please use tlvince-semantic-release-bundle-bump-bot.foo() instead of tlvince-semantic-release-bundle-bump-bot.bar() from now on.

Thank you,

– Bundle Bump Bot ❤️

@tlvince tlvince closed this Sep 22, 2015
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.

1 participant