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

The automated logic for setting NPM package version and Token List version should not be in complete sync #17

Open
kasparkallas opened this issue Aug 2, 2023 · 1 comment
Assignees

Comments

@kasparkallas
Copy link
Contributor

The package.json should be able to move independently from the token list versions and vice versa. Although when the token list version gets bumped, the equivelant should be bumped for the package.json.

image

@kasparkallas
Copy link
Contributor Author

Note that we've moved to a monorepo structure where the root version and the NPM package version can be different.

Now the root version can reflect the token list version. The NPM package version can move faster than the root version. Whenever the token list is bumped then the NPM package should probably be bumped in similar fashion.

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

No branches or pull requests

2 participants