search

ithaka / pharos

JSTOR's design system
https://pharos.jstor.org
MIT License
119 stars 15 forks source link

Infra: Allow alpha/beta releases #731

Open michael-iden opened 6 months ago

michael-iden commented 6 months ago

The problem A few weeks ago we were looking to have a change with the tabs component available for us to use in our project but the ability to use pharos with the change reflected, even after PR merge, was blocked on needing a major release. This caused fair bit of discussion and pressure to complete the final pharos changes for the major release on an accelerated timeline. Also once released, we noticed a few bugs or regressions that needed immediate resolution

The solution Allow us to build alpha/beta releases for next major versions so consumers that need those features are not blocked. Also it will give us the ability to more comprehensively validate behavior by getting the changes in the hands of consumers as soon as possible.

Alternatives considered Current behavior is to wait for all changes we have roadmapped to get into the next major release before cutting a new version.

Additional information N/A

daneah commented 6 months ago

@michael-iden et al. the docs from Atlassian on prereleases with Changesets may prove useful.

Niznikr commented 6 months ago

Have had a pretty good experience using a feature/release branch and entering prerelease mode. With that, the Changesets action knows to generate prerelease PRs to merge and publish.

daneah commented 6 months ago

Thanks for sharing your experience and the example @Niznikr!