Release 2025-01-16

[jpsantosbh]

Description

Release SDKs

Type of change

• Internal refactoring
• Bug fix (bugfix - non-breaking)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Code snippets

In case of new feature or breaking changes, please include code snippets.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9a5a446

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[iAmmar7]

Hey @jpsantosbh, this might sound stupid since we still have not yet made this an automated process, but just wanted to highlight all the changelog.md needs minor changes.

1. The project details should come at the start of the md file.
2. The MAJOR, MINOR, and PATCH, should be changed into Added, Changed, and Fixed.
3. The version title needs to follow this pattern: [M.M.P] - YYYY-MM-DD

[iAmmar7]

This might be wrong, considering the repository URL.

[jpsantosbh]

npm WARN publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm WARN publish errors corrected:
npm WARN publish "repository.url" was normalized to "git+https://github.com/signalwire/signalwire-js.git"

I had this error when I was publishing the release. then I just executed npm pkg fix, and that change was introduced.

[iAmmar7]

Okay, thanks! I did not know that.

[iAmmar7]

Suggested change

	### Modified
	### Changed

[iAmmar7]

Also, can you please update this change in other changelog files as well?

[iAmmar7]

Okay, thanks! I did not know that.

[iAmmar7]

Also, can you fix the date in the PR title, please? Release 2025-02-03. We might need to update if we do not merge this PR today.

[jpsantosbh]

Isn't the date the date when we publish to npm?

[iAmmar7]

Isn't the date the date when we publish to npm?

True, we release to the NPM when we merge this PR. So, the date needs to change if we merge it tomorrow.

[jpsantosbh]

@iAmmar7 But we did the release already.
this PR is only to sync the main with what has been released.

NPM will reject the new publish with the same version that is already there. so this date is already fine.

[iAmmar7]

@iAmmar7 But we did the release already. this PR is only to sync the main with what has been released.

NPM will reject the new publish with the same version that is already there. so this date is already fine.

Alright.

@Devon-White, could you please prepare the release notes and update the docs if that's necessary.