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

BAAS-22176: bump to v2 #122

Closed
wants to merge 1 commit into from
Closed

Conversation

Gabri3l
Copy link

@Gabri3l Gabri3l commented Jun 12, 2024

No description provided.

Copy link

@kpatel71716 kpatel71716 left a comment

Choose a reason for hiding this comment

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

[q] could we could make a v2 tag from the realm branch? Or is the intention to start versioning each of the individual packages for more granular versioning?

Not opposed to either approach, just curious. If we are going with the latter, this lgtm

@Gabri3l
Copy link
Author

Gabri3l commented Jun 12, 2024

[q] could we could make a v2 tag from the realm branch? Or is the intention to start versioning each of the individual packages for more granular versioning?

Not opposed to either approach, just curious. If we are going with the latter, this lgtm

Still doing the tags, IIUC you gotta do this for major versions in go. From baas I can't just use v2.0.0 I have to use goja/v2 v2.0.0 which is why this PR is needed. We can still go back ahah

@kpatel71716
Copy link

Still doing the tags, IIUC you gotta do this for major versions in go. From baas I can't just use v2.0.0 I have to use goja/v2 v2.0.0 which is why this PR is needed. We can still go back ahah

Ah, TIL, works for me then!

Copy link

@kpatel71716 kpatel71716 left a comment

Choose a reason for hiding this comment

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

LGTM!

@Gabri3l
Copy link
Author

Gabri3l commented Jun 13, 2024

Won't do, I don't think this is worth it every time we make a breaking change to the mem usage. It might also conflict with an eventual v2 of goja and make things confusing.

@Gabri3l Gabri3l closed this Jun 13, 2024
@Gabri3l Gabri3l deleted the BAAS-22176-v2 branch June 13, 2024 14:08
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.

2 participants