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

Bump github.com/nikoksr/notify from 0.41.1 to 1.0.1 #81

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 28, 2024

Bumps github.com/nikoksr/notify from 0.41.1 to 1.0.1.

Release notes

Sourced from github.com/nikoksr/notify's releases.

v1.0.1

What's Changed

Full Changelog: nikoksr/notify@v1.0.0...v1.0.1

v1.0.0

Upgrading to v1.0.0

I'm proud to announce that Notify has reached version 1.0.0.

Why v1.0.0?

  1. API Stability: While Notify has been at v0.x for a while, the API is to be considered stable at this point. Moving to v1.0.0 formalizes this stability and signals a commitment to semantic versioning going forward.

  2. Breaking Changes: This version includes some breaking changes. Moving to v1.0.0 allows me to properly communicate these changes in line with semver principles.

  3. Commitment to Stability: I'm prioritizing API stability for v1.x over continuous optimization. While I acknowledge that the current API may have some imperfections, I'm choosing to embrace it as-is to provide a consistent experience for users.

What This Means for Users

  • Future breaking changes will be reflected in major version bumps (2.0.0, 3.0.0, etc.).
  • Minor and patch versions will maintain backwards compatibility within the v1.x line.
  • I'm committed to maintaining v1.x while working on future improvements.

Looking Ahead

I'm actively working on v2 in the background, which will address any inconsistencies in the current API. However, my focus for v1.x is on providing a stable, reliable API that users can depend on. I believe this approach offers the best balance between progress and stability.

Thank you for your continued support and trust in Notify. I'm excited about this milestone and the future of the project!

What's Changed

... (truncated)

Commits
  • d8b163c chore(deps): update and tidy Go dependencies (#875)
  • 3f7d4ed fix(deps): update module github.com/go-lark/lark to v1.15.0 (#860)
  • 19fee1e fix(deps): update module github.com/atc0005/go-teams-notify/v2 to v2.13.0 (#864)
  • 7c7e59c fix(deps): update aws-sdk-go-v2 monorepo (#861)
  • e50ffcf fix(deps): update module github.com/silenceper/wechat/v2 to v2.1.7 (#873)
  • 23f7fe0 chore(deps): update dependency go to v1.23.2 (#858)
  • 03870e5 ci(lint): update and fix golangci-lint (#874)
  • 7eae8e8 fix(deps): update module google.golang.org/api to v0.192.0 (#859)
  • 88abae2 fix(deps): update module github.com/mailgun/mailgun-go/v4 to v4.15.0 (#857)
  • aeebabd docs(readme): minor changes
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies dependencies go Pull requests that update Go code labels Oct 28, 2024
Copy link

what-the-diff bot commented Oct 28, 2024

PR Summary

  • Dependency Version Update

    • The component github.com/nikoksr/notify that our software relies on has been updated from version v0.41.1 to a new version v1.0.1. This update could either provide new functionalities, improve performance, or fix errors that were present in the previous version.
  • Indirect Dependency Removal

    • An unnecessary component github.com/pkg/errors that our software used to require has been removed. This allows our software to be lighter and potentially perform better, while also reducing the possibility of facing any errors or issues related to this component.

Bumps [github.com/nikoksr/notify](https://github.com/nikoksr/notify) from 0.41.1 to 1.0.1.
- [Release notes](https://github.com/nikoksr/notify/releases)
- [Commits](nikoksr/notify@v0.41.1...v1.0.1)

---
updated-dependencies:
- dependency-name: github.com/nikoksr/notify
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/nikoksr/notify-1.0.1 branch from 1691acf to d4a554e Compare October 28, 2024 20:11
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 4, 2024

Superseded by #83.

@dependabot dependabot bot closed this Nov 4, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/nikoksr/notify-1.0.1 branch November 4, 2024 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies dependencies go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants