Currently we have automation around pushing a template tag (eg spin/templates/v1.0) for each new Spin release.
However, it depends on the automated sdk bump PR be merged specifically via a merge commit. If merged via another approach, say via rebase, the automation won't run, as it relies on data only present on a merge commit event (eg github.event.commits[0].author.name == 'fermybot').
We should improve the robustness of this automation so it will run as intended regardless of how the sdk bump PR is merged into main.
Currently we have automation around pushing a template tag (eg
spin/templates/v1.0
) for each new Spin release.However, it depends on the automated sdk bump PR be merged specifically via a merge commit. If merged via another approach, say via rebase, the automation won't run, as it relies on data only present on a merge commit event (eg
github.event.commits[0].author.name == 'fermybot'
).We should improve the robustness of this automation so it will run as intended regardless of how the sdk bump PR is merged into
main
.