chore: bump version to 1.3.0#28
Draft
oerlandsen wants to merge 2 commits into
Draft
Conversation
Author
|
@JoMarchant podi revisar que esto calce con tu release porfa |
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
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 release v1.3.0 quedó a medias: el tag y el release en GitHub existen desde junio, pero nunca se hizo el bump de versión ni se publicó la gema. En RubyGems seguimos en 1.2.0, así que nadie que instale
fintoctiene los onboardings de entities ni el manager de webhook endpoints.¿Qué hay de nuevo?
Alineo el repo con el release que ya existe:
version.rba 1.3.0entities.create, manager de webhook endpoints y soporte multipart en el clienteGemfile.lockactualizadoTests
No hay cambios de código, solo versión y changelog. La suite corre igual en CI.
Safety Checks
Consideraciones
Ojo: el tag v1.3.0 actual apunta a un commit donde
version.rbtodavía dice 1.2.0, así que si alguien buildea la gema desde el tag le sale unafintoc-1.2.0.gem. Después de mergear esto hay que mover el tag (o recrear el release) al commit del merge, y recién ahí publicar a RubyGems con la cuentafintoc(pide MFA).