search

notaryproject / notation-core-go

Contains support for Notary Project signature envelope, and format specific implementation
Apache License 2.0
14 stars 28 forks source link

build(deps): bump github.com/veraison/go-cose from 1.1.0 to 1.3.0 #232

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 month ago

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: https://github.com/veraison/go-cose/compare/v1.1.0...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: https://github.com/veraison/go-cose/compare/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 will merge this PR once it's up-to-date and CI passes on it, as requested by @shizhMSFT.

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 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)
codecov[bot] commented 1 month ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.29%. Comparing base (4819e1d) to head (8c06c16). Report is 1 commits behind head on main.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #232 +/- ## ======================================= Coverage 91.29% 91.29% ======================================= Files 30 30 Lines 2608 2608 ======================================= Hits 2381 2381 Misses 173 173 Partials 54 54 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

shizhMSFT commented 2 weeks ago

@dependabot merge

dependabot[bot] commented 2 weeks ago

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

JeyJeyGao commented 1 week ago

@dependabot rebase