Update tag_and_release.yml

[Dargon789]

Summary by Sourcery

Overhaul the tag_and_release workflow to trigger on v* tag pushes, adjust permissions, and use the GitHub CLI for creating releases

CI:

• Trigger tag_and_release workflow on push events for tags matching v*
• Grant contents write permission for the workflow
• Replace actions/create-release action with a GitHub CLI command in a dedicated release job
• Run the release job on ubuntu-24.04

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's Guide

Refactor the tag_and_release workflow to trigger only on tag pushes, tighten permissions, restructure the release job, and switch from the actions/create-release action to a GitHub CLI invocation.

Flow diagram for new release creation process in workflow

flowchart TD
  Start([Start: Tag push event]) --> Step1["Trigger tag_and_release workflow"]
  Step1 --> Step2["Run release job"]
  Step2 --> Step3["Set GITHUB_TOKEN and tag variables"]
  Step3 --> Step4["Run gh release create command"]
  Step4 --> End([End: Release created])

Loading

File-Level Changes

Change	Details	Files
Scope workflow to tag pushes and explicit permissions	Added on.push.tags filter for v* tags Set permissions.contents to write	.github/workflows/tag_and_release.yml
Restructure release job	Defined a dedicated 'release' job with a descriptive name Updated runs-on to ubuntu-24.04 Adjusted job and step indentation and naming	.github/workflows/tag_and_release.yml
Replace create-release action with GitHub CLI	Removed actions/create-release@… step Added run step invoking 'gh release create' with github.ref_name Moved tag and title logic into shell command and generate notes	.github/workflows/tag_and_release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
interface-web-veej	Error			Oct 1, 2025 2:48pm

[cloudflare-workers-and-pages]

Deploying uniswap with    Cloudflare Pages

Latest commit:	5352be4
Status:	✅  Deploy successful!
Preview URL:	https://d3b2fb16.uniswap-omj.pages.dev
Branch Preview URL:	https://dargon789-patch-2.uniswap-omj.pages.dev

View logs

[sourcery-ai]

Hey there - I've reviewed your changes and found some issues that need to be addressed.

• The workflow is invalid YAML because you’ve nested on: and jobs: inside a step—move them to the top level of the file.
• Add a step to install or configure the GitHub CLI (for example using actions/setup-gh) before running gh release create.
• Include an actions/checkout step so that the GitHub CLI has the correct repository context when creating the release.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The workflow is invalid YAML because you’ve nested `on:` and `jobs:` inside a step—move them to the top level of the file.
- Add a step to install or configure the GitHub CLI (for example using actions/setup-gh) before running `gh release create`.
- Include an `actions/checkout` step so that the GitHub CLI has the correct repository context when creating the release.

## Individual Comments

### Comment 1
<location> `.github/workflows/tag_and_release.yml:38-40` </location>
<code_context>
-        uses: actions/create-release@8e3b4a5e184b498423d5b25ca5ceb5a9258c92c2
+      - name: 🪽 Create release
+      
+        on:
+          push:
+          tags:
+            - v*
+
</code_context>

<issue_to_address>
**issue (bug_risk):** Workflow triggers are misplaced inside a job definition.

Move the 'on:' block to the root of the workflow file to ensure proper triggering.
</issue_to_address>

### Comment 2
<location> `.github/workflows/tag_and_release.yml:43-44` </location>
<code_context>
+          tags:
+            - v*
+
+          permissions:
+          contents: write
+
+      jobs:
</code_context>

<issue_to_address>
**issue (bug_risk):** Permissions block is incorrectly nested under workflow triggers.

Move the 'permissions:' block outside of the 'on:' block to avoid YAML parsing errors and ensure permissions are applied correctly.
</issue_to_address>

### Comment 3
<location> `.github/workflows/tag_and_release.yml:46-47` </location>
<code_context>
+          permissions:
+          contents: write
+
+      jobs:
+          release:
+          name: Release pushed tag
+          runs-on: ubuntu-24.04
</code_context>

<issue_to_address>
**issue (bug_risk):** Job definitions are incorrectly nested under a job.

Move the 'jobs:' block to the top level of the workflow file to ensure correct execution.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)