Closed ctmbl closed 2 years ago
The second method you propose is definitely the good one for long term. I think soon the backend and frontend development will be separated (for the best) We should still be able to track the version of each one and release a global version for the website when needed. So it's ok for me! Just I think you forgot to add the version in frontend/package.json
Did you manage to find some documentation on removing an existing tag?
you should be able to simply
git tag --delete v0.0.1
git checkout 31e96b3
git tag v0.1.0 -m "blah blah"
git push --tags --prune
:+1:
What about
frontend/package.json
?in
nushell
, i getnushell> [. frontend backend] | each { |it| open $"($it)/package.json" | get version } â•â”€â”€â”€â”¬â”€â”€â”€â”€â”€â”€â”€â•® │ 0 │ 0.1.0 │ │ 1 │ 0.1.0 │ │ 2 │ 0.1.0 │ ╰───┴───────╯
is there anything to do in
frontend/package.json
? :thinking:
here is a PR for the first official version bump of the website.
Some questions must be address:
frontend/package.json
andbackend/package.json
with same version (because for now there are developed at the same time)frontend/package.json
,backend/package.json
AND a rootpackage.json
indicating the version of the WHOLE website (the solution I chose in this PR :heart: )v0.0.1
(I think we let it as it is and jump to next version)The wiki will have be updated after this discussion Right after this merging we will tag the commit with
v0.1.0
HURRY UP this PR must be resolved before any other (especially #17) you have my point of view please give yours @atxr @amtoine