Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump github.com/veraison/go-cose from 1.1.0 to 1.3.0 #55

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 27, 2024

Bumps github.com/veraison/go-cose from 1.1.0 to 1.3.0.

Release notes

Sourced from github.com/veraison/go-cose's releases.

v1.3.0

What's Changed

New Contributors

Full Changelog: veraison/go-cose@v1.2.1...v1.3.0

v1.3.0-rc.1

Cutting rc.1 based on no changes to alpha.1 https://github.com/veraison/go-cose/blob/main/release-management.md#pre-release

Full Changelog: veraison/go-cose@v1.3.0-alpha.1...v1.3.0-rc.1

v1.3.0-alpha.1

What's Changed

... (truncated)

Changelog

Sourced from github.com/veraison/go-cose's changelog.

go-cose Release Management

Overview

This document describes [go-cose][go-cose] project release management, which includes release criteria, versioning, supported releases, and supported upgrades.

The go-cose project maintainers strive to provide a stable go-lang implementation for interacting with [COSE][ietf-cose] constructs. Stable implies appropriate and measured changes to the library assuring consumers have the necessary functionality to interact with COSE objects. If you or your project require added functionality, or bug fixes, please open an issue or create a pull request. The project welcomes all contributions from adding functionality, implementing testing, security reviews to the release management. Please see here for how to contribute.

The maintainers may periodically update this policy based on feedback.

Release Versioning

Consumers of the go-cose module may reference main directly, or reference released tags.

All go-cose [releases][releases] follow a go-lang flavored derivation (v*) of the [semver][sem-ver] format, with optional pre-release labels.

Logical Progression of a release: v1.0.0-alpha.1 --> v1.0.0-alpha.2 --> v1.0.0-rc.1 --> v1.0.0

A new major or minor release will not have an automated release posted until the branch reaches alpha quality.

  • All versions use a preface of v
  • Given a version vX.Y.Z,
  • Optional -alpha.n | -rc.n pre-release version
    • Each incremental alpha or rc build will bump the suffix (n) number.
    • It's not expected to have more than 9 alphas or rcs. The suffix will be a single digit.
    • If > 9 builds do occur, the format will simply use two digit indicators (v1.0.0-alpha.10)

[!IMPORTANT] Pre-releases will NOT use the github pre-release flag.

Branch Management

To meet the projects stability goals, go-cose does not currently operate with multiple feature branches. All active development happens in main. For each release, a branch is created for servicing, following the versioning name. v1.0.0-alpha-1 would have an associated v1.0.0-alpha.1 branch. All version and branch names are lower case.

Major Releases

As a best practice, consumers should opt-into new capabilities through major releases. The go-cose project will not add new functionality to patches or minor releases as this could create a new surface area that may be exploited.

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/veraison/go-cose](https://github.com/veraison/go-cose) from 1.1.0 to 1.3.0.
- [Release notes](https://github.com/veraison/go-cose/releases)
- [Changelog](https://github.com/veraison/go-cose/blob/main/release-management.md)
- [Commits](veraison/go-cose@v1.1.0...v1.3.0)

---
updated-dependencies:
- dependency-name: github.com/veraison/go-cose
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 27, 2024
@zosocanuck zosocanuck merged commit b8f99d3 into main Sep 27, 2024
5 checks passed
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/veraison/go-cose-1.3.0 branch September 27, 2024 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant