632bbf948d
When we blast off again, we check out a commit so the current branch ends up being incorrect and is HEAD rather than X-Y-Z. This therefore no longer just runs git rev-parse --abbrev-ref HEAD; it instead checks to ensure that the result of that call matches the release branch pattern. If it doesn't, it fetches the containing branch for the commit. Since we only ever blast off from bump commits, we can safely assume that only one release branch will ever contain the bump commit and therefore be the one we want to use when tagging the release on npm. |
||
|---|---|---|
| .. | ||
| tls | ||
| __init__.py | ||
| config.py | ||
| env_util.py | ||
| git.py | ||
| gn.py | ||
| native_tests.py | ||
| npm.py | ||
| npx.py | ||
| patches.py | ||
| util.py | ||
| utils.js | ||
| version-utils.js | ||