Skip to content

Conversation

@josephjclark
Copy link
Collaborator

This PR just switches pre-releases back on

Do no merge until Lightning is ready

@josephjclark
Copy link
Collaborator Author

josephjclark commented Jul 1, 2024

Oh hey, I need to check that the doc site ignores next tags!

EDIT: I don't think any action is needed, because:

  • next tags are not published to github, only to npm. So they don't appear in the version list
  • draft PRs do not trigger a doc site rebuild, so next docs won't be included

Basically so long as no next stuff is merged to main, and so long as no next tags are generated and pushed to github (and they won't be, because changeset doesn't even see the next versions), the doc site will be totally unaffected.

Nice.

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