Fixes the release pipeline #119
Conversation
JayShortway
changed the title
| release-tags-job: &release-tags-job | ||
| filters: | ||
| tags: | ||
| only: /^[0-9]+\.[0-9]+\.[0-9]+(?!.*-SNAPSHOT).*$/ |
There was a problem hiding this comment.
I don't think we tag snapshots right? I believe snapshots the way we do them in android/iOS is done automatically on every push to the main branch.
There was a problem hiding this comment.
Also, I wonder if we should just copye the existing release-tags alias in iOS/Android, where we basically ignore just some specific tags and release everything else... Mostly to be consistent.
There was a problem hiding this comment.
We don't tag them indeed, but this was intended to be defensive against the potential case when we push a tag (e.g. for reference purposes) that we don't want to release. This matches all strings that start with a semver, with any suffix except "SNAPSHOT".
I'm okay to make it less strict to make it behave like iOS/Android, but I think it should still be a single regex for consistency with the workflow filter.
Fixes the release pipeline
Adds release tag filters to jobs as well.
As the title says. CircleCI is weird. This bug seems to have existed for a long time where workflows with a tag filter need to have the same filter on jobs as well.
One of many: https://discuss.circleci.com/t/running-a-workflow-after-tagging-commit/49581.
Without this change, we get a "No workflow" state from CircleCI.
After this change, the workflow runs.
Disables configuration cache for the publish task
This is not supported.