Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: changelog #327

Merged
merged 1 commit into from
Nov 11, 2024
Merged

fix: changelog #327

merged 1 commit into from
Nov 11, 2024

Conversation

ponderingdemocritus
Copy link
Contributor

@ponderingdemocritus ponderingdemocritus commented Nov 11, 2024

Summary by CodeRabbit

  • Chores
    • Enhanced the release process with a new step to retrieve the latest version tag.
    • Added functionality to check for a CHANGELOG.md file and generate a release body accordingly.
    • Simplified the GitHub release naming and removed conditional logic for the prerelease field.

Copy link

coderabbitai bot commented Nov 11, 2024

Walkthrough

The pull request modifies the .github/workflows/release.yaml file to enhance the release process. It introduces a new step to retrieve the latest version tag and another step to generate the release body based on the existence of a CHANGELOG.md file. The "Create GitHub Release" step is updated to use the new version tag and simplifies the release name. The prerelease field is hardcoded to false, streamlining the overall release workflow.

Changes

File Path Change Summary
.github/workflows/release.yaml - Added "Get Version Tag" step to retrieve the latest version tag.
- Added "Generate Release Body" step to read CHANGELOG.md if it exists.
- Updated "Create GitHub Release" to use the new version tag and simplified the release name.
- Hardcoded prerelease field to false.

Possibly related PRs

  • fix: Improve release #322: The changes in this PR also modify the .github/workflows/release.yaml file, focusing on enhancing the release process, which is directly related to the modifications made in the main PR.

Poem

🐰 In the garden of code, where the releases bloom,
A tag now appears, dispelling the gloom.
With changelogs in hand, we craft our delight,
Each version a treasure, shining so bright!
Hooray for the updates, let the bunnies cheer,
For smoother releases, we hold dear! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Outside diff range and nitpick comments (1)
.github/workflows/release.yaml (1)

Line range hint 3-11: Add input validation for release_type.

The workflow accepts release_type as input but doesn't validate it against the allowed values.

Add a validation step after the checkout:

    - name: Validate Release Type
      run: |
        valid_types="prerelease prepatch patch minor preminor major"
        if ! echo "$valid_types" | grep -w "${{ github.event.inputs.release_type }}" > /dev/null; then
          echo "Error: Invalid release_type. Must be one of: $valid_types"
          exit 1
        fi
🧰 Tools
🪛 actionlint

50-50: shellcheck reported issue in this script: SC2086:info:1:49: Double quote to prevent globbing and word splitting

(shellcheck)


54-54: shellcheck reported issue in this script: SC2086:info:2:38: Double quote to prevent globbing and word splitting

(shellcheck)


54-54: shellcheck reported issue in this script: SC2086:info:4:58: Double quote to prevent globbing and word splitting

(shellcheck)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 00e829f and 0260c42.

📒 Files selected for processing (1)
  • .github/workflows/release.yaml (1 hunks)
🧰 Additional context used
🪛 actionlint
.github/workflows/release.yaml

50-50: shellcheck reported issue in this script: SC2086:info:1:49: Double quote to prevent globbing and word splitting

(shellcheck)


54-54: shellcheck reported issue in this script: SC2086:info:2:38: Double quote to prevent globbing and word splitting

(shellcheck)


54-54: shellcheck reported issue in this script: SC2086:info:4:58: Double quote to prevent globbing and word splitting

(shellcheck)

Comment on lines +48 to +51
- name: Get Version Tag
id: get_tag
run: echo "TAG=$(git describe --tags --abbrev=0)" >> $GITHUB_OUTPUT

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add error handling and fix shell quoting.

The tag retrieval step needs better error handling and shell safety.

- echo "TAG=$(git describe --tags --abbrev=0)" >> $GITHUB_OUTPUT
+ if ! tag=$(git describe --tags --abbrev=0); then
+   echo "Error: No tags found in the repository"
+   exit 1
+ fi
+ echo "TAG=${tag}" >> "$GITHUB_OUTPUT"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Get Version Tag
id: get_tag
run: echo "TAG=$(git describe --tags --abbrev=0)" >> $GITHUB_OUTPUT
- name: Get Version Tag
id: get_tag
run: |
if ! tag=$(git describe --tags --abbrev=0); then
echo "Error: No tags found in the repository"
exit 1
fi
echo "TAG=${tag}" >> "$GITHUB_OUTPUT"
🧰 Tools
🪛 actionlint

50-50: shellcheck reported issue in this script: SC2086:info:1:49: Double quote to prevent globbing and word splitting

(shellcheck)

Comment on lines +52 to +60
- name: Generate Release Body
id: release_body
run: |
if [ -f CHANGELOG.md ]; then
echo "body=$(cat CHANGELOG.md)" >> $GITHUB_OUTPUT
else
echo "body=No changelog provided for this release." >> $GITHUB_OUTPUT
fi

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Improve changelog handling reliability.

The current implementation has potential race conditions and shell safety issues.

   run: |
-    if [ -f CHANGELOG.md ]; then
-      echo "body=$(cat CHANGELOG.md)" >> $GITHUB_OUTPUT
-    else
-      echo "body=No changelog provided for this release." >> $GITHUB_OUTPUT
-    fi
+    if [ ! -f CHANGELOG.md ]; then
+      echo "body=No changelog provided for this release." >> "$GITHUB_OUTPUT"
+      exit 0
+    fi
+    # Validate changelog is not empty
+    if [ ! -s CHANGELOG.md ]; then
+      echo "Error: CHANGELOG.md exists but is empty"
+      exit 1
+    fi
+    # Use heredoc to handle multiline content safely
+    {
+      echo "body<<EOF"
+      cat CHANGELOG.md
+      echo "EOF"
+    } >> "$GITHUB_OUTPUT"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Generate Release Body
id: release_body
run: |
if [ -f CHANGELOG.md ]; then
echo "body=$(cat CHANGELOG.md)" >> $GITHUB_OUTPUT
else
echo "body=No changelog provided for this release." >> $GITHUB_OUTPUT
fi
- name: Generate Release Body
id: release_body
run: |
if [ ! -f CHANGELOG.md ]; then
echo "body=No changelog provided for this release." >> "$GITHUB_OUTPUT"
exit 0
fi
# Validate changelog is not empty
if [ ! -s CHANGELOG.md ]; then
echo "Error: CHANGELOG.md exists but is empty"
exit 1
fi
# Use heredoc to handle multiline content safely
{
echo "body<<EOF"
cat CHANGELOG.md
echo "EOF"
} >> "$GITHUB_OUTPUT"
🧰 Tools
🪛 actionlint

54-54: shellcheck reported issue in this script: SC2086:info:2:38: Double quote to prevent globbing and word splitting

(shellcheck)


54-54: shellcheck reported issue in this script: SC2086:info:4:58: Double quote to prevent globbing and word splitting

(shellcheck)

Comment on lines +65 to +71
PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
with:
tag_name: ${{ steps.tag_publish.outputs.TAG }}
release_name: Release ${{ steps.tag_publish.outputs.TAG }}
tag_name: ${{ steps.get_tag.outputs.TAG }}
release_name: Release
body_path: CHANGELOG.md
draft: false
prerelease: ${{ contains(github.event.inputs.release_type, 'pre') }}
prerelease: false
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Critical: Update deprecated action and fix body handling.

Several issues need attention:

  1. The actions/create-release@v1 action is deprecated
  2. There's an inconsistency between the generated release body and body_path usage
  3. Hardcoding prerelease: false removes flexibility previously provided by the release_type input

Consider these improvements:

  1. Replace the deprecated action with the newer GitHub CLI approach:
- uses: actions/create-release@v1
- env:
-   GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-   PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
- with:
-   tag_name: ${{ steps.get_tag.outputs.TAG }}
-   release_name: Release
-   body_path: CHANGELOG.md
-   draft: false
-   prerelease: false
+ run: |
+   gh release create "${{ steps.get_tag.outputs.TAG }}" \
+     --title "Release" \
+     --notes "${{ steps.release_body.outputs.body }}" \
+     --draft=false \
+     --prerelease=${{ github.event.inputs.release_type == 'prerelease' }}
+ env:
+   GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  1. Restore the conditional prerelease logic based on the release_type input to maintain workflow flexibility.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
with:
tag_name: ${{ steps.tag_publish.outputs.TAG }}
release_name: Release ${{ steps.tag_publish.outputs.TAG }}
tag_name: ${{ steps.get_tag.outputs.TAG }}
release_name: Release
body_path: CHANGELOG.md
draft: false
prerelease: ${{ contains(github.event.inputs.release_type, 'pre') }}
prerelease: false
run: |
gh release create "${{ steps.get_tag.outputs.TAG }}" \
--title "Release" \
--notes "${{ steps.release_body.outputs.body }}" \
--draft=false \
--prerelease=${{ github.event.inputs.release_type == 'prerelease' }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

@ponderingdemocritus ponderingdemocritus merged commit 75be133 into main Nov 11, 2024
3 checks passed
@ponderingdemocritus ponderingdemocritus deleted the changelog branch November 11, 2024 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant