Upgrading to v1.0.0
I'm proud to announce that Notify has reached version 1.0.0.
Why v1.0.0?
-
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.
-
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.
-
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
- chore(deps): update actions/cache action to v4 by @renovate in #816
- chore(deps): update mcr.microsoft.com/devcontainers/go docker tag to v1 by @renovate in #842
- chore(deps): update golangci/golangci-lint-action action to v6 by @renovate in #841
- chore(deps): update github/codeql-action action to v3 by @renovate in #794
- chore(deps): update codecov/codecov-action action to v4 by @renovate in #829
- chore(deps): update actions/setup-go action to v5 by @renovate in #788
- fix(notify)!: resolve test & linter issues and fix dependencies compatibility by @nikoksr in #847
Full Changelog: v0.41.1...v1.0.0