You've already forked goreleaser
mirror of
https://github.com/goreleaser/goreleaser.git
synced 2025-07-15 01:34:21 +02:00
09be848e1a
Continuing on #5308 and #5307, this finally adds Zig support to GoReleaser! Things are very raw still, plenty of use cases to test (please do test on your project if you can), but it does work at least for simple projects! A release done by this: https://github.com/goreleaser/example-zig/releases/tag/v0.1.0 --------- Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
73 lines
3.3 KiB
Zig
Generated
73 lines
3.3 KiB
Zig
Generated
.{
|
|
// This is the default name used by packages depending on this one. For
|
|
// example, when a user runs `zig fetch --save <url>`, this field is used
|
|
// as the key in the `dependencies` table. Although the user can choose a
|
|
// different name, most users will stick with this provided value.
|
|
//
|
|
// It is redundant to include "zig" in this name because it is already
|
|
// within the Zig package namespace.
|
|
.name = "proj",
|
|
|
|
// This is a [Semantic Version](https://semver.org/).
|
|
// In a future version of Zig it will be used for package deduplication.
|
|
.version = "0.0.0",
|
|
|
|
// This field is optional.
|
|
// This is currently advisory only; Zig does not yet do anything
|
|
// with this value.
|
|
//.minimum_zig_version = "0.11.0",
|
|
|
|
// This field is optional.
|
|
// Each dependency must either provide a `url` and `hash`, or a `path`.
|
|
// `zig build --fetch` can be used to fetch all dependencies of a package, recursively.
|
|
// Once all dependencies are fetched, `zig build` no longer requires
|
|
// internet connectivity.
|
|
.dependencies = .{
|
|
// See `zig fetch --save <url>` for a command-line interface for adding dependencies.
|
|
//.example = .{
|
|
// // When updating this field to a new URL, be sure to delete the corresponding
|
|
// // `hash`, otherwise you are communicating that you expect to find the old hash at
|
|
// // the new URL.
|
|
// .url = "https://example.com/foo.tar.gz",
|
|
//
|
|
// // This is computed from the file contents of the directory of files that is
|
|
// // obtained after fetching `url` and applying the inclusion rules given by
|
|
// // `paths`.
|
|
// //
|
|
// // This field is the source of truth; packages do not come from a `url`; they
|
|
// // come from a `hash`. `url` is just one of many possible mirrors for how to
|
|
// // obtain a package matching this `hash`.
|
|
// //
|
|
// // Uses the [multihash](https://multiformats.io/multihash/) format.
|
|
// .hash = "...",
|
|
//
|
|
// // When this is provided, the package is found in a directory relative to the
|
|
// // build root. In this case the package's hash is irrelevant and therefore not
|
|
// // computed. This field and `url` are mutually exclusive.
|
|
// .path = "foo",
|
|
|
|
// // When this is set to `true`, a package is declared to be lazily
|
|
// // fetched. This makes the dependency only get fetched if it is
|
|
// // actually used.
|
|
// .lazy = false,
|
|
//},
|
|
},
|
|
|
|
// Specifies the set of files and directories that are included in this package.
|
|
// Only files and directories listed here are included in the `hash` that
|
|
// is computed for this package. Only files listed here will remain on disk
|
|
// when using the zig package manager. As a rule of thumb, one should list
|
|
// files required for compilation plus any license(s).
|
|
// Paths are relative to the build root. Use the empty string (`""`) to refer to
|
|
// the build root itself.
|
|
// A directory listed here means that all files within, recursively, are included.
|
|
.paths = .{
|
|
"build.zig",
|
|
"build.zig.zon",
|
|
"src",
|
|
// For example...
|
|
//"LICENSE",
|
|
//"README.md",
|
|
},
|
|
}
|