chore(deps): bump go.einride.tech/sage from 0.201.1 to 0.314.0 in /.sage

Bumps [go.einride.tech/sage](https://github.com/einride/sage) from 0.201.1 to 0.314.0.
- [Release notes](https://github.com/einride/sage/releases)
- [Commits](einride/sage@v0.201.1...v0.314.0)

---
updated-dependencies:
- dependency-name: go.einride.tech/sage
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

.goreleaser.yml

@@ -1,3 +1,4 @@
+version: 2
 before:
   hooks:
     - go mod download
@@ -10,14 +11,6 @@ builds:
       - windows
       - darwin
 
-archives:
-  - replacements:
-      darwin: Darwin
-      linux: Linux
-      windows: Windows
-      386: i386
-      amd64: x86_64
-
 checksum:
   name_template: "checksums.txt"
 

.sage/go.mod

@@ -2,4 +2,4 @@ module sage
 
 go 1.17
 
-require go.einride.tech/sage v0.201.1
+require go.einride.tech/sage v0.314.0

.sage/go.sum

@@ -1,2 +1,2 @@
-go.einride.tech/sage v0.201.1 h1:O5ydNh3UbSjklu+2fGzztFNSVLmHd8T5snoTt7phzdQ=
-go.einride.tech/sage v0.201.1/go.mod h1:EzV5uciFX7/2ho8EKB5K9JghOfXIxlzs694b+Tkl5GQ=
+go.einride.tech/sage v0.314.0 h1:PcJQD7yk+U9+nvGDOGXNV91cywzoHn540MxJRpu+w+E=
+go.einride.tech/sage v0.314.0/go.mod h1:EzV5uciFX7/2ho8EKB5K9JghOfXIxlzs694b+Tkl5GQ=

.sage/sagefile.go

@@ -9,8 +9,7 @@ import (
 	"go.einride.tech/sage/tools/sggo"
 	"go.einride.tech/sage/tools/sggolangcilint"
 	"go.einride.tech/sage/tools/sggoreleaser"
-	"go.einride.tech/sage/tools/sggoreview"
-	"go.einride.tech/sage/tools/sgmarkdownfmt"
+	"go.einride.tech/sage/tools/sgmdformat"
 	"go.einride.tech/sage/tools/sgyamlfmt"
 )
 
@@ -30,7 +29,7 @@ func main() {
 }
 
 func All(ctx context.Context) error {
-	sg.Deps(ctx, ConvcoCheck, GoLint, GoReview, GoTest, FormatMarkdown, FormatYAML)
+	sg.Deps(ctx, ConvcoCheck, GoLint, GoTest, FormatMarkdown, FormatYAML)
 	sg.SerialDeps(ctx, Proto.All, TypescriptLint)
 	sg.SerialDeps(ctx, GoModTidy, GitVerifyNoDiff)
 	return nil
@@ -51,19 +50,14 @@ func GoTest(ctx context.Context) error {
 	return sggo.TestCommand(ctx).Run()
 }
 
-func GoReview(ctx context.Context) error {
-	sg.Logger(ctx).Println("reviewing Go files...")
-	return sggoreview.Command(ctx, "-c", "1", "./...").Run()
-}
-
 func GoLint(ctx context.Context) error {
 	sg.Logger(ctx).Println("linting Go files...")
 	return sggolangcilint.Run(ctx)
 }
 
 func FormatMarkdown(ctx context.Context) error {
 	sg.Logger(ctx).Println("formatting Markdown files...")
-	return sgmarkdownfmt.Command(ctx, "-w", ".").Run()
+	return sgmdformat.Command(ctx).Run()
 }
 
 func ConvcoCheck(ctx context.Context) error {
@@ -94,7 +88,7 @@ func GoReleaser(ctx context.Context, snapshot bool) error {
 	}
 	args := []string{
 		"release",
-		"--rm-dist",
+		"--clean",
 	}
 	if len(sggit.Tags(ctx)) == 0 && !snapshot {
 		sg.Logger(ctx).Printf("no git tag found for %s, forcing snapshot mode", sggit.ShortSHA(ctx))

CODE_OF_CONDUCT.md

@@ -1,87 +1,128 @@
-Contributor Covenant Code of Conduct
-====================================
+# Contributor Covenant Code of Conduct
 
-Our Pledge
-----------
+## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
 
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
 
-Our Standards
--------------
+## Our Standards
 
-Examples of behavior that contributes to a positive environment for our community include:
+Examples of behavior that contributes to a positive environment for our
+community include:
 
--	Demonstrating empathy and kindness toward other people
--	Being respectful of differing opinions, viewpoints, and experiences
--	Giving and gracefully accepting constructive feedback
--	Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
--	Focusing on what is best not just for us as individuals, but for the overall community
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
 
 Examples of unacceptable behavior include:
 
--	The use of sexualized language or imagery, and sexual attention or advances of any kind
--	Trolling, insulting or derogatory comments, and personal or political attacks
--	Public or private harassment
--	Publishing others' private information, such as a physical or email address, without their explicit permission
--	Other conduct which could reasonably be considered inappropriate in a professional setting
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
-Enforcement Responsibilities
-----------------------------
+## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
 
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
 
-Scope
------
+## Scope
 
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
 
-Enforcement
------------
+## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at open-source@einride.tech.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+open-source@einride.tech.
 
 All complaints will be reviewed and investigated promptly and fairly.
 
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
 
-Enforcement Guidelines
-----------------------
+## Enforcement Guidelines
 
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
 
 ### 1. Correction
 
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
 
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
 
 ### 2. Warning
 
-**Community Impact**: A violation through a single incident or series of actions.
+**Community Impact**: A violation through a single incident or series of
+actions.
 
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
 
 ### 3. Temporary Ban
 
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
 
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
 
 ### 4. Permanent Ban
 
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
 
-**Consequence**: A permanent ban from any sort of public interaction within the community.
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
 
-Attribution
------------
+## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+This Code of Conduct is adapted from the
+[Contributor Covenant](https://www.contributor-covenant.org), version 2.0,
+available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
 
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
 
-For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

Makefile

@@ -10,7 +10,7 @@ sagefile := $(abspath $(cwd)/.sage/bin/sagefile)
 go := $(shell command -v go 2>/dev/null)
 export GOWORK ?= off
 ifndef go
-SAGE_GO_VERSION ?= 1.18.4
+SAGE_GO_VERSION ?= 1.20.2
 export GOROOT := $(abspath $(cwd)/.sage/tools/go/$(SAGE_GO_VERSION)/go)
 export PATH := $(PATH):$(GOROOT)/bin
 go := $(GOROOT)/bin/go
@@ -78,10 +78,6 @@ ifndef snapshot
 endif
 	@$(sagefile) GoReleaser "$(snapshot)"
 
-.PHONY: go-review
-go-review: $(sagefile)
-	@$(sagefile) GoReview
-
 .PHONY: go-test
 go-test: $(sagefile)
 	@$(sagefile) GoTest

README.md

@@ -1,15 +1,16 @@
-protoc-gen-typescript-aip
-=========================
+# protoc-gen-typescript-aip
 
-Generates Typescript helpers for Protobuf APIs conforming to [AIP](https://aip.dev).
+Generates Typescript helpers for Protobuf APIs conforming to
+[AIP](https://aip.dev).
 
 ### Install the plugin
 
 ```bash
 go get go.einride.tech/protoc-gen-typescript-aip
 ```
 
-Or download a prebuilt binary from [releases](https://github.com/einride/protoc-gen-typescript-aip/releases).
+Or download a prebuilt binary from
+[releases](https://github.com/einride/protoc-gen-typescript-aip/releases).
 
 ### Invocation
 
@@ -45,14 +46,15 @@ exclude_resource_definitions
                         in the file scope, only on messages. Default: false.
 ```
 
----
+______________________________________________________________________
 
-Features
---------
+## Features
 
 ### Resource names
 
-Generates helpers for working with resource names, based on [ResourceDescriptor](https://github.com/googleapis/googleapis/blob/master/google/api/resource.proto) annotations.
+Generates helpers for working with resource names, based on
+[ResourceDescriptor](https://github.com/googleapis/googleapis/blob/master/google/api/resource.proto)
+annotations.
 
 #### Example
 

SECURITY.md

@@ -1,28 +1,40 @@
-Security Policy
-===============
+# Security Policy
 
-Einride welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in relation to this project, we want to hear from you. This policy outlines steps for reporting security issues to us, what we expect, and what you can expect from us.
+Einride welcomes feedback from security researchers and the general public to
+help improve our security. If you believe you have discovered a vulnerability,
+privacy issue, exposed data, or other security issues in relation to this
+project, we want to hear from you. This policy outlines steps for reporting
+security issues to us, what we expect, and what you can expect from us.
 
-Supported versions
-------------------
+## Supported versions
 
-We release patches for security issues according to semantic versioning. This project is currently unstable (v0.x) and only the latest version will receive security patches.
+We release patches for security issues according to semantic versioning. This
+project is currently unstable (v0.x) and only the latest version will receive
+security patches.
 
-Reporting a vulnerability
--------------------------
+## Reporting a vulnerability
 
-Please do not report security vulnerabilities through public issues, discussions, or change requests.
+Please do not report security vulnerabilities through public issues,
+discussions, or change requests.
 
-Please report security issues via [oss-security@einride.tech](mailto:oss-security@einride.tech). Provide all relevant information, including steps to reproduce the issue, any affected versions, and known mitigations. The more details you provide, the easier it will be for us to triage and fix the issue. You will receive a response from us within 2 business days. If the issue is confirmed, a patch will be released as soon as possible.
+Please report security issues via
+[oss-security@einride.tech](mailto:oss-security@einride.tech). Provide all
+relevant information, including steps to reproduce the issue, any affected
+versions, and known mitigations. The more details you provide, the easier it
+will be for us to triage and fix the issue. You will receive a response from us
+within 2 business days. If the issue is confirmed, a patch will be released as
+soon as possible.
 
-For more information, or security issues not relating to open source code, please consult our [Vulnerability Disclosure Policy](https://www.einride.tech/vulnerability-disclosure-policy).
+For more information, or security issues not relating to open source code,
+please consult our
+[Vulnerability Disclosure Policy](https://www.einride.tech/vulnerability-disclosure-policy).
 
-Preferred languages
--------------------
+## Preferred languages
 
 English is our preferred language of communication.
 
-Contributions and recognition
------------------------------
+## Contributions and recognition
 
-We appreciate every contribution and will do our best to publicly [acknowledge](https://einride.tech/security-acknowledgments.txt) your contributions.
+We appreciate every contribution and will do our best to publicly
+[acknowledge](https://einride.tech/security-acknowledgments.txt) your
+contributions.

example/proto/Makefile

@@ -10,7 +10,7 @@ sagefile := $(abspath $(cwd)/../../.sage/bin/sagefile)
 go := $(shell command -v go 2>/dev/null)
 export GOWORK ?= off
 ifndef go
-SAGE_GO_VERSION ?= 1.18.4
+SAGE_GO_VERSION ?= 1.20.2
 export GOROOT := $(abspath $(cwd)/../../.sage/tools/go/$(SAGE_GO_VERSION)/go)
 export PATH := $(PATH):$(GOROOT)/bin
 go := $(GOROOT)/bin/go