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.

Sign up for GitHub

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

Jump to bottom

Prepare for v3.1.0 release #571

Merged
merged 2 commits into from
Jan 9, 2025
Merged

Prepare for v3.1.0 release #571

merged 2 commits into from
Jan 9, 2025
+426 −137

Conversation

kpcraig
Copy link
Contributor

@kpcraig kpcraig commented Jan 9, 2025

Description

Updates dependencies to prepare for release

fairclothjm
fairclothjm approved these changes Jan 9, 2025
View reviewed changes
Copy link
Contributor

@fairclothjm fairclothjm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Should we go ahead and update the changelog and dist/index.js (if necessary) for the release? That would prevent us from needing another PR to do the release.

@kpcraig
Copy link
Contributor Author

kpcraig commented Jan 9, 2025

I picked 3.1.0 instead of 3.0.1 or 4.0.0 on vibes (we added a couple things but existing workflows should still work).

Also, I didn't get any dist/index.js changes on npm run build, which might be expected for only transitive dependency changes?

@fairclothjm fairclothjm changed the title dependency updates to prepare for release Prepare for v3.1.0 release Jan 9, 2025
@kpcraig kpcraig merged commit a1b77a0 into main Jan 9, 2025
6 checks passed
@kpcraig kpcraig deleted the VAULT-33323/update-deps branch January 9, 2025 18:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fairclothjm fairclothjm fairclothjm approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@kpcraig @fairclothjm