Bump: Main Package Version #62
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
oops, sorry i had actually missed to bump the version when releasing |
|
What is the situation here? |
|
Hi, im doing some internal vite migrations to support new features. Will do
a new release after that
…On Fri, Mar 8, 2024 at 10:40 PM Žan Fras (FrozenSpirit) < ***@***.***> wrote:
What is the situation here?
—
Reply to this email directly, view it on GitHub
<#62 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADGCQC5FUVJGS2ONLJAZ263YXHWGRAVCNFSM6AAAAABB34YBT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWGA4DGOBYGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hey, im doing a new release with bumped up version which uses new vite5 for the development |
|
Thanks for the contribution @zuhno |
|
Released the new version 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have updated the version in the main package.(1.3.2 -> 1.3.4, 1.3.3 is already released) Once this PR is merged, I will pull again and push PR(#61).
One thing I'm curious about is whether it's correct for contributors to update the main package version themselves? It seems like it could be challenging to manage versions with multiple contributors. 🥲