Skip to content

fix(ci): remove dst: . from GoReleaser archive config#598

Merged
Aureliolo merged 1 commit intomainfrom
fix/windows-installer-archive
Mar 19, 2026
Merged

fix(ci): remove dst: . from GoReleaser archive config#598
Aureliolo merged 1 commit intomainfrom
fix/windows-installer-archive

Conversation

@Aureliolo
Copy link
Copy Markdown
Owner

@Aureliolo Aureliolo commented Mar 19, 2026 •
edited by coderabbitai bot
Loading

Summary

  • Remove dst: . from GoReleaser archive files config to fix Windows installer failure
  • The dst: . directive creates a literal . directory entry in zip archives, causing PowerShell's Expand-Archive to fail with "Can not process invalid archive entry '.'"
  • Removing it uses GoReleaser's default behavior of placing files at the archive root -- LICENSE still lands alongside the binary without the problematic entry

Root Cause

GoReleaser's dst: . in the archive files section is interpreted differently by zip vs tar.gz:

  • tar.gz (Linux/macOS): tar handles . entries natively -- no issue
  • zip (Windows): Creates a literal . directory entry that Expand-Archive rejects

Test plan

  • Built snapshot archives with goreleaser release --snapshot --clean
  • Verified zip contains only LICENSE and synthorg.exe (no . entry)
  • Verified tar.gz contains only LICENSE and synthorg (no . entry)
  • Tested Expand-Archive on the fixed zip -- extracts successfully
  • Ran synthorg.exe version from extracted archive -- works

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated release archive configuration to streamline packaging while maintaining LICENSE file inclusion.

@Aureliolo @claude
fix(ci): remove dst: . from GoReleaser archive config
3a801a4 
The `dst: .` directive creates a literal `.` directory entry in zip
archives, causing PowerShell's Expand-Archive to fail with "Can not
process invalid archive entry '.'". Removing it uses GoReleaser's
default behavior of placing files at the archive root.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@gemini-code-assist
Copy link
Copy Markdown
Contributor

gemini-code-assist bot commented Mar 19, 2026

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical issue affecting Windows installations by modifying the GoReleaser configuration. The change prevents the creation of an invalid directory entry within zip archives, ensuring that the installer can correctly extract files and that the application functions as expected on Windows systems.

Highlights

  • GoReleaser Configuration Update: Removed the dst: . directive from the GoReleaser archive files configuration for the LICENSE file.
  • Windows Installer Fix: Resolved an issue where the dst: . directive created a problematic literal . directory entry in zip archives, causing PowerShell's Expand-Archive to fail on Windows.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 19, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 19, 2026 •
edited
Loading

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5156fc9f-4a33-476d-9a5a-f09bf5e21820

📥 Commits

Reviewing files that changed from the base of the PR and between e2d86a3 and 3a801a4.

📒 Files selected for processing (1)
  • cli/.goreleaser.yml
💤 Files with no reviewable changes (1)
  • cli/.goreleaser.yml

Walkthrough

The GoReleaser configuration in cli/.goreleaser.yml was updated. Specifically, the destination mapping for the LICENSE file in the archives section of the default archive format was removed, while the source reference remains intact. The explicit dst: . directive is no longer present. No other build, archive, checksum, or release settings were modified.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: removing dst: . from GoReleaser archive config to fix Windows installer failures.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@Aureliolo Aureliolo merged commit c8bf862 into main Mar 19, 2026
38 checks passed
@Aureliolo Aureliolo deleted the fix/windows-installer-archive branch March 19, 2026 15:22
@Aureliolo Aureliolo mentioned this pull request Mar 19, 2026
Merged
@gemini-code-assist
Copy link
Copy Markdown
Contributor

gemini-code-assist bot commented Mar 19, 2026

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

Aureliolo added a commit that referenced this pull request Mar 19, 2026
@Aureliolo
chore(main): release 0.3.8 (#599)
e6a11a3 
🤖 I have created a release *beep* *boop*
---


##
[0.3.8](v0.3.7...v0.3.8)
(2026-03-19)


### Features

* dynamic settings UI with auto-discovery and basic/advanced toggle
([#600](#600))
([11b32b7](11b32b7))


### Bug Fixes

* **ci:** remove dst: . from GoReleaser archive config
([#598](#598))
([c8bf862](c8bf862))
* **engine:** wire compaction_callback and plan_execute_config through
auto-selection
([#601](#601))
([795327f](795327f))
* harden setup wizard completion and status checks
([#616](#616))
([d99d7b7](d99d7b7))


### Maintenance

* add /codebase-audit skill for deep parallel codebase auditing
([#613](#613))
([db02320](db02320))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Aureliolo