Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/bump-gitstream-core.yml
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,6 @@ jobs:
git push origin HEAD:${{ env.BRANCH_NAME }}
gh pr create \
--base develop \
--title "Bump `@linearb/gitstream-core` to `${{ env.VERSION }}`" \
--title "Bump \`@linearb/gitstream-core\` to \`${{ env.VERSION }}\`" \
--body-file pr_description.txt \
--head ${{ env.BRANCH_NAME }} ${{ env.REVIEWER_ARG }} ${{ env.LABEL_ARG }}
25 changes: 17 additions & 8 deletions .github/workflows/create-tag-on-merge.yml
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,11 @@ jobs:
core.setOutput('pr-title', pr.title);
core.setOutput('release-notes', releaseNote);
core.setOutput('pr-number', pr.number);


// Check if CHANGELOG is present using the same logic as above
const hasChangelog = pr.body && pr.body.match(/__CHANGELOG__\s*(.*?)\s*_Generated by LinearB AI/s);
core.setOutput('has-changelog', !!hasChangelog);

return pr.labels.some(label => label.name.includes('auto-deploy'));
}
return false;
Expand All @@ -80,14 +84,19 @@ jobs:
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
# Create release notes using printf to handle special characters safely
printf "## What's Changed\n\n%s in [#%s](https://github.com/${{ github.repository }}/pull/%s)\n\n%s\n" \
"${{ steps.should-deploy.outputs.pr-title }}" \
"${{ steps.should-deploy.outputs.pr-number }}" \
"${{ steps.should-deploy.outputs.pr-number }}" \
"${{ steps.should-deploy.outputs.release-notes }}" > release_notes.md
if [ "${{ steps.should-deploy.outputs.has-changelog }}" = "true" ]; then
# Use custom release notes from CHANGELOG
printf "## What's Changed\n\n%s in [#%s](https://github.com/${{ github.repository }}/pull/%s)\n\n%s\n" \
"${{ steps.should-deploy.outputs.pr-title }}" \
"${{ steps.should-deploy.outputs.pr-number }}" \
"${{ steps.should-deploy.outputs.pr-number }}" \
"${{ steps.should-deploy.outputs.release-notes }}" > release_notes.md
gh release create $NEW_TAG --notes-file release_notes.md
else
# Use GitHub's automatic release notes generation
gh release create $NEW_TAG --generate-notes
fi

gh release create $NEW_TAG --notes-file release_notes.md
git checkout $NEW_TAG
npm run update-v2-tag

Expand Down