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

Release Updates #3900

Closed
wants to merge 5 commits into from
Closed

Release Updates #3900

wants to merge 5 commits into from

Conversation

bdbch
Copy link
Contributor

@bdbch bdbch commented Mar 28, 2023

This PR includes a few changes on our publish scripts & CI to allow independent versions again (2.0.0 preparation).

@bdbch bdbch requested a review from svenadlung March 28, 2023 13:48
@bdbch bdbch self-assigned this Mar 28, 2023
@netlify
Copy link

netlify bot commented Mar 28, 2023

Deploy Preview for tiptap-embed ready!

Name Link
🔨 Latest commit a8ff2aa
🔍 Latest deploy log https://app.netlify.com/sites/tiptap-embed/deploys/6422f030ffce390008ca7c8f
😎 Deploy Preview https://deploy-preview-3900--tiptap-embed.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@rfgamaral
Copy link
Contributor

Are you folks still aiming to complete the 2.0.0 milestone issues before the final release?

@bdbch
Copy link
Contributor Author

bdbch commented Mar 28, 2023

@rfgamaral yes - but we'll need to move the lists to 2.1.0 for now. Our plan is to move to 2.1.0-rc.1 right after 2.0.0 is released so if you want you could directly test the new version afterwards.

I'm pretty much done with the lists, but don't have the time to completely test the list delete/backspace changes before our deadline and I'd rather have a version to test before pushing it to stable for now.

Hope that's okay since you were already waiting for a bit right now.

So far we're pretty close to get 2.0.0 out - right now we're doing a lot of preparation (versioning, preparing releasing, docs updates, etc.) so as soon as this done I could imagine releasing 2.0.0 and move to work directly on 2.1.0 afterwards.

@rfgamaral
Copy link
Contributor

@bdbch It's understandable 👍 I was just looking to get a grasp on the current state and roadmap. Thanks.

@bdbch bdbch closed this Mar 28, 2023
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.

None yet

2 participants