release: v0.2.2#45
Merged
Merged
Conversation
ahinrif
approved these changes
May 15, 2026
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
2 participants
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.
Description
Recovery del run de Release. El workflow falló en
release/finalizeporque la Appfin-releasesno estaba en el bypass del ruleset "Protect main", solo la había agregado en el branch protection clásico, pero el ruleset es un sistema aparte.Resultado del run:
@fintoc/cli@0.2.2publicado en npm ✓v0.2.2en remote (apuntando a este commit huérfano) ✓main❌Este PR sube el commit huérfano a
main. Después hay que crear el Release entry a mano:Eso dispara automáticamente
update-homebrew.ymly la fórmula de homebrew queda en 0.2.2.Ya agregué
fin-releasesal ruleset bypass.Requirements
None — el commit ya existe en remote bajo el tag.
Additional changes
None.