chore: create v1.0.0 release for Hackathon FIAP 2026#80
Conversation
Agent-Logs-Url: https://github.com/fiap-tech-challenge-java/vigisus/sessions/c22588b3-0bec-4688-9712-9300c54cb4f2 Co-authored-by: rebecanonato89 <38442994+rebecanonato89@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e85b634949
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| uses: softprops/action-gh-release@v2 | ||
| with: | ||
| tag_name: v1.0.0 | ||
| target_commitish: main |
There was a problem hiding this comment.
Using target_commitish: main makes the v1.0.0 tag resolve to whatever commit is at the tip of main when the job executes, not necessarily the commit that triggered the workflow. If another push lands on main before this job runs, this release can point to the wrong code snapshot. Pinning to ${{ github.sha }} (or the dispatch SHA) avoids that race and keeps the release reproducible.
Useful? React with 👍 / 👎.
Adds a GitHub Actions workflow that automatically creates the
v1.0.0release when merged tomain.Release details:
v1.0.0mainHEADVigiSUS v1.0.0 — Hackathon FIAP 2026The workflow triggers on push to
main(scoped to changes to this workflow file) and also supportsworkflow_dispatchfor manual runs. It usessoftprops/action-gh-release@v2withcontents: writepermissions to create and publish the release.