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

Version 1.1.0 to set in package.json ? #219

Closed
eden91940 opened this issue Nov 12, 2022 · 2 comments · Fixed by #228
Closed

Version 1.1.0 to set in package.json ? #219

eden91940 opened this issue Nov 12, 2022 · 2 comments · Fixed by #228

Comments

@eden91940
Copy link

"version": "1.0.0",

@ZeroEkkusu
Copy link
Collaborator

If the version is in package.json doesn’t matter, we can also set it to ”V1”.

@mds1
Copy link
Collaborator

mds1 commented Nov 12, 2022

Since we're not publishing to NPM currently, this doesn't matter much, but it will matter if/when we do start publishing to npm (#39, #170). So let's PR in a change to "1.1.0" to keep it in sync for good measure, but I don't think we need to do a new release/tag just for this

mds1 added a commit that referenced this issue Nov 19, 2022
accidentally skipped v1.1.0 in package.json, see #219
mds1 added a commit that referenced this issue Nov 19, 2022
accidentally skipped v1.1.0 in package.json, see #219
mds1 added a commit that referenced this issue Dec 15, 2022
accidentally skipped v1.1.0 in package.json, see #219
mds1 added a commit that referenced this issue Dec 15, 2022
accidentally skipped v1.1.0 in package.json, see #219
@mds1 mds1 closed this as completed in #228 Dec 15, 2022
thomas-lamb-tech pushed a commit to thomas-lamb-tech/std_forge that referenced this issue Dec 26, 2024
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 a pull request may close this issue.

3 participants