fix(core): migra tag prerelease de dev a alpha#87
Merged
Conversation
… dev a beta
semver considera "dev > beta" alfabeticamente, por lo que rush bloquea
la promocion 4.0.14-dev.N a 4.0.14-beta.0 al verla como degradacion.
cambios:
- script github-actions.js: mapa rama a tag { dev: alpha, beta, next }
- version-policies.json: -dev.N a -alpha.N (preserva contadores)
- package.json de 16 paquetes: -dev.N a -alpha.N
- test plano sin dependencias (node common/scripts/github-actions.test.js)
nota para consumidores: npm install @cfdi/<pkg>@dev pasa a @Alpha
MisaelMa
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contexto
El CI bloquea el PR
dev → betacon:Razón: SemVer ordena los tags de prerelease alfabéticamente.
dev>beta, por lo que4.0.14-dev.5 > 4.0.14-beta.0y Rush trata la promoción como una degradación y aborta.Solución
La rama
devsigue existiendo como rama git, pero pasa a publicar en npm con tagalpha(nodev). Así:Rush ya no ve la promoción
dev → betacomo degradación porquebeta > alpha.Cambios
common/scripts/github-actions.js: mapabranchToTag = { dev: 'alpha', beta: 'beta', next: 'next' }. El comandorush version --override-prerelease-idahora usa el tag mapeado, no el nombre de la rama.common/config/rush/version-policies.json: todos los-dev.N→-alpha.Npreservando los contadores.packages/**/package.json(16 archivos): mismo renombre.common/scripts/github-actions.test.js(nuevo): test sin dependencias externas, corre connode.Flujo final
devalpha4.0.14-alpha.5betabeta4.0.14-beta.0mainlatest4.0.14Transiciones que ahora funcionan sin error:
feature/X → dev:4.0.14-alpha.5 → 4.0.14-alpha.6✅dev → beta:4.0.14-alpha.5 → 4.0.14-beta.0✅ (era el error)fix/Y → beta:4.0.14-beta.2 → 4.0.14-beta.3✅beta → main:4.0.14-beta.3 → 4.0.14✅Test plan
node common/scripts/github-actions.test.js— 12/12 passedfeature/X → devpublique con tagalphadev → betaoriginal y verificar que no chocaNota para consumidores
Quien hacía
npm install @cfdi/<pkg>@devdebe pasar a@alphadespués del próximo release. Las versiones-dev.Nya publicadas en npm no se borran, solo dejan de recibir actualizaciones.