chore: release main

[aversini]

User description

🤖 I have created a release beep boop

auth-common: 3.0.0

3.0.0 (2024-07-19)

⚠ BREAKING CHANGES

• the params are now an object

Features

• adding body as a possible option for getting token (#117) (768a977)

---

This PR was generated with Release Please. See documentation.

---

PR Type

Other

---

Description

• Updated version for auth-common package to 3.0.0 in .release-please-manifest.json.
• Added changelog entry for auth-common version 3.0.0, including breaking changes and new features.
• Updated version number in packages/auth-common/package.json to 3.0.0.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	.release-please-manifest.json Update version in release-please manifest                                .release-please-manifest.json Updated version for auth-common package from 2.12.1 to 3.0.0. +1/-1      package.json Bump version to 3.0.0 in package.json                                        packages/auth-common/package.json Updated version number from 2.12.1 to 3.0.0. +1/-1
Documentation	CHANGELOG.md Add changelog for version 3.0.0 with breaking changes        packages/auth-common/CHANGELOG.md Added changelog entry for version 3.0.0. Noted breaking changes: params are now an object. Added feature: body as a possible option for getting token. +11/-0

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Enhancement	Enhance the changelog descriptions for better clarity and guidance on the changes Add more detailed descriptions under the "BREAKING CHANGES" and "Features" sections in the changelog to provide better clarity on what specifically has changed, how it impacts existing functionality, and how users should adapt their implementations. packages/auth-common/CHANGELOG.md [8-12] -* the params are now an object -* adding body as a possible option for getting token +* The parameter structure for API calls has been changed to an object format to enhance readability and flexibility. Ensure to update your function calls accordingly. +* Added support for including a body payload in token retrieval requests, allowing more versatile authentication mechanisms. Apply this suggestion Suggestion importance[1-10]: 9 Why: Providing detailed descriptions in the changelog is essential for users to understand the impact of changes and how to adapt their implementations, improving overall clarity and usability.	9
Possible issue	Verify and adjust the version number to accurately reflect the nature of changes Ensure that the version bump from "2.12.1" to "3.0.0" in the .release-please-manifest.json is intentional and correctly reflects a major version change due to breaking changes or significant new features. If the change is not meant to be a major version update, consider adjusting the version number to reflect the appropriate update level (patch or minor). .release-please-manifest.json [3] -"packages/auth-common": "3.0.0" +"packages/auth-common": "2.13.0" # Adjusted to minor version bump if breaking changes are not intended Apply this suggestion Suggestion importance[1-10]: 8 Why: This suggestion is important as it ensures the version bump is intentional and correctly reflects the nature of the changes, which is crucial for maintaining proper versioning and avoiding confusion for users.	8
Best practice	Ensure version alignment with semantic versioning and update dependencies accordingly Confirm that the version update in package.json aligns with the semantic versioning rules based on the changes listed in the changelog. If the changes are indeed breaking, ensure that all dependencies and consumers of this package are updated or notified about these changes. packages/auth-common/package.json [3] -"version": "3.0.0" +"version": "3.0.0" # Confirm and ensure alignment with semantic versioning Apply this suggestion Suggestion importance[1-10]: 7 Why: Confirming the version update aligns with semantic versioning rules is a good practice to ensure consistency and proper communication of changes, although it is somewhat redundant with the first suggestion.	7

[github-actions]

Bundle Size

Status	File	Size (Gzip)	Limits
✅	index.js	17.75 KB (+4 B +0.02%)	18 kb

Overall bundle size: 17.75 KB (+4 B +0.02%)
Overall status: ✅

[aversini]

🤖 Created releases:

• auth-common-v3.0.0
  🌻