Skip to content

Commit

Permalink
Updated sfreleaser doctor with new error
Browse files Browse the repository at this point in the history
  • Loading branch information
maoueh committed Jul 17, 2024
1 parent d0a8414 commit 1cc4c1c
Show file tree
Hide file tree
Showing 2 changed files with 25 additions and 1 deletion.
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Ensure `sfreleaser` works with Goreleaser 2.x

> [!IMPORTANT]
> You will need to use an up to date version of `goreleaser/goreleaser-cross:v1.22` or later for `sfreleaser` to work properly.
> You will need to use an up to date version of `goreleaser/goreleaser-cross:v1.22` or later for `sfreleaser` to work properly. If you have an error of the form `⨯ release failed after 0s error=only configurations files on version: 1 are supported, yours is version: 2 , please update your configuration`, update your image to latest version using `docker pull --platform linux/arm64 goreleaser/goreleaser-cross:v1.22` and ensure you `.sfreleaser` does use it properly.
- Fixed wrong error when a project was never release.

Expand Down
24 changes: 24 additions & 0 deletions cmd/sfreleaser/doctor.go
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,30 @@ func doctor(cmd *cobra.Command, _ []string) error {
fmt.Println(cli.Dedent(`
Here a list of known issues and possible solutions:
##
### X release failed after 0s error=only configurations files on version: 1 are supported, yours is version: 2 , please update your configuration
##
This happens when you are using a newer 'sfreleaser' version (>= v0.8.0) but that the Docker image 'goreleaser/goreleaser-cross' used for the
building is too old. Indeed, newer versions of 'goreleaser-cross' uses Goreleaser version > 2.0 which brings a bunch of breaking changes.
The 'sfreleaser' tool only works with Goreleaser version >= 2.0.0. First check the project's '.sfreleaser', if there is
release:
goreleaser-docker-image: <something>
Ensure the image is based on latest 'goreleaser-cross:1.22' or later. If you were using a custom image,
update it the base to use 'goreleaser/goreleaser-cross:1.22' or later.
If you are not using a custom image and still have the problem, you might need to re-pull the
image, it assume you have it because we do not specify the patch version, only the major and minor.
This can be done with the following command:
docker pull --platform=linux/arm64 goreleaser/goreleaser-cross:1.22
> **Note**
> Change --platform=linux/arm64 to your platform if you are not on ARM64.
##
### Unable to copy command PTY to stdout: read /dev/ptmx: input/output error
##
Expand Down

0 comments on commit 1cc4c1c

Please sign in to comment.