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

Version Packages #1167

Merged
merged 1 commit into from
Jan 18, 2025
Merged

Version Packages #1167

merged 1 commit into from
Jan 18, 2025

Conversation

pmcelhaney
Copy link
Owner

@pmcelhaney pmcelhaney commented Jan 18, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/main branch 2 times, most recently from ae3368c to e859c2b Compare January 18, 2025 18:27
@pmcelhaney pmcelhaney enabled auto-merge January 18, 2025 18:44
@pmcelhaney pmcelhaney closed this Jan 18, 2025
auto-merge was automatically disabled January 18, 2025 19:15

Pull request was closed

@pmcelhaney pmcelhaney reopened this Jan 18, 2025
@github-actions github-actions bot force-pushed the changeset-release/main branch from e859c2b to 092de9d Compare January 18, 2025 19:23
@pmcelhaney pmcelhaney enabled auto-merge January 18, 2025 21:07
@pmcelhaney pmcelhaney closed this Jan 18, 2025
auto-merge was automatically disabled January 18, 2025 21:07

Pull request was closed

@pmcelhaney pmcelhaney reopened this Jan 18, 2025
@pmcelhaney pmcelhaney merged commit 278dcbd into main Jan 18, 2025
5 checks passed
@pmcelhaney pmcelhaney deleted the changeset-release/main branch January 18, 2025 21:28
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.

path property on HTTP_PUT type is never even though spec defines a path parameter
1 participant