[FOLIO-895] Review publish procedure for pre-release dependencies Created: 13/Oct/17 Updated: 18/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Michal Kuklis | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | build-release | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | |||||||||||||
| Development Team: | Core: Platform | ||||||||||||
| Description |
|
It's currently still not clear how to handle publishing procedure for pre-release dependencies. "Tag name must not be a valid SemVer range: v3.0.0-pre.1" Ideally it would be great to just create a new tag and then point to it from other places in a similar fashion to what we've done with a commit hash. For example instead of: “@folio/stripes-connect”: “folio-org/stripes-connect#3c2714a189c2296f389fc6ee4e79a7ee7c962949" do: “@folio/stripes-connect”: “folio-org/stripes-connect#v3.0.0-pre.1" |
| Comments |
| Comment by Michal Kuklis [ 13/Oct/17 ] |
|
It looks like these steps work:
|
| Comment by Matthew Jones [ 13/Oct/17 ] |
|
As just tested, Michal Kuklis was able to publish version 3.0.0-pre.1 of stripes-connect. Observations: 1) A subsequent commit to stripes-connect created a CI snapshot that dropped part of the pre-release -pre.n suffix. The result was 3.0.0-pre00010 and not 3.0.0-pre.100010 (Perhaps to be more clear, 3.0.0-pre.1.00010, though this would differ slightly from current snapshots which cannot have an extra segment) 2) Even with this mangled pre-release suffix, after reinstalling my stripes-core dependencies with stripes-connect at ^3.0.0-pre.1 it pulled down 3.0.0-pre00010 from npm-folioci. At the moment, it seems CI should be updated to better tolerate the -pre.n suffix when creating build snapshots. |