-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
✨ housekeeping: Improve docs and make help (#228)
- Document release process. - Make first README.md link point to evy.dev rather than scratch. - Replace sponsorship red heart emoji with a white one for readability. Update `make help` awk scripts for multi-line comments on top or rather than next to target. Add `/version` endpoint to deployment. This merges the following commits: * tools: Update `make help` scripting * docs: Replace sponsorship heart emoji * docs: Make first README.md link point to evy.dev * docs: Add releasing documentation * frontend: Add version endpoint Makefile | 74 +++++++++++++++++++++++++---------- README.md | 5 ++- docs/development/releasing.md | 30 ++++++++++++++ firebase/firebase.json | 6 +++ 4 files changed, 92 insertions(+), 23 deletions(-) Pull-Request: #228
- Loading branch information
Showing
4 changed files
with
92 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Releasing | ||
|
||
Evy automatically releases with every new merge to the `main` branch on GitHub. | ||
This process publishes artifacts for all major operating systems and | ||
architectures under [releases] as part of a successful CI run. Additionally, | ||
the `evylang/tap/evy` brew formula is updated to the latest version. | ||
|
||
By default, each release receives a semantic **patch** bump. For example, if the | ||
latest version is `v0.2.4`, the next one will be `v0.2.5` by default. | ||
|
||
To trigger a minor version bump, add a new file to the | ||
[release-notes directory]. A minor version bump indicates the completion of a | ||
[milestone]. The release notes file should be named according to the new | ||
version, for example, `v0.2.0.md`. | ||
|
||
To trigger a **minor** version bump a new file must be added to the | ||
[release-notes directory]. A minor version bump signifies the completion of a | ||
milestone. The release notes file is named according to the new version, for | ||
example `v0.2.0.md`. | ||
|
||
Evy's current major version is still 0, this may change in the future. | ||
Evy's language syntax, tooling, and public API are still under development | ||
and not yet considered stable. Additionally, for major version 0, the meaning | ||
of patch and minor versions does not conform to the standard | ||
[semantic versioning specifications]. | ||
|
||
[releases]: https://github.com/evylang/evy/releases | ||
[milestone]: https://github.com/evylang/evy/milestones | ||
[release-notes directory]: https://github.com/evylang/evy/tree/main/docs/release-notes | ||
[semantic versioning specifications]: https://semver.org/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters