Skip to content

Release v0.19.0#598

Merged
hacdias merged 13 commits intoreleasefrom
release-v0.19.0
Apr 9, 2024
Merged

Release v0.19.0#598
hacdias merged 13 commits intoreleasefrom
release-v0.19.0

Conversation

@hacdias
Copy link
Copy Markdown
Member

@hacdias hacdias commented Apr 9, 2024

No description provided.

hacdias and others added 13 commits February 20, 2024 09:48
we already return base58, but we did not support them as input.
libp2p specs state implementations MUST support both, it is also better
for end users if we are liberal in inputs and support both notations:
https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md#string-representation
* chore: bump go.mod to Go 1.21 and run go fix

* chore: run go mod tidy

* chore: bump go.mod to Go 1.21 and run go fix

* chore: run go mod tidy

* chore: CHANGELOG.md

---------

Co-authored-by: Marcin Rataj <lidel@lidel.org>
@hacdias hacdias added the release Merging this PR will create a tagged release label Apr 9, 2024
@hacdias hacdias self-assigned this Apr 9, 2024
@hacdias hacdias requested a review from a team as a code owner April 9, 2024 09:49
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 9, 2024

Suggested version: v0.19.0

Comparing to: v0.18.0 (diff)

Changes in go.mod file(s):

(empty)

gorelease says:

# diagnostics
go.mod: the following requirements are needed
	go.opentelemetry.io/otel/exporters/jaeger@v1.14.0
	go.uber.org/atomic@v1.11.0
Run 'go mod tidy' to add missing requirements.
required module github.com/microcosm-cc/bluemonday@v1.0.1 retracted by module author: Retract older versions as only latest is to be depended upon

# summary
Suggested version: v0.18.1

gocompat says:

Your branch is up to date with 'origin/release'.

Cutting a Release (and modifying non-markdown files)

This PR is modifying both version.json and non-markdown files.
The Release Checker is not able to analyse files that are not checked in to release. This might cause the above analysis to be inaccurate.
Please consider performing all the code changes in a separate PR before cutting the release.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 9, 2024

Codecov Report

Attention: Patch coverage is 58.65385% with 43 lines in your changes are missing coverage. Please review.

Project coverage is 60.37%. Comparing base (c336fc9) to head (76648b7).

Impacted file tree graph

@@             Coverage Diff             @@
##           release     #598      +/-   ##
===========================================
- Coverage    65.71%   60.37%   -5.35%     
===========================================
  Files          207      229      +22     
  Lines        25612    22106    -3506     
===========================================
- Hits         16831    13346    -3485     
+ Misses        7312     7279      -33     
- Partials      1469     1481      +12     
Files Coverage Δ
routing/http/types/json/responses.go 57.69% <100.00%> (+12.23%) ⬆️
bitswap/options.go 41.02% <0.00%> (-3.42%) ⬇️
routing/http/server/server.go 71.85% <82.50%> (+4.39%) ⬆️
provider/provider.go 26.82% <40.74%> (+26.82%) ⬆️

... and 213 files with indirect coverage changes

@hacdias hacdias merged commit b50fcfd into release Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release Merging this PR will create a tagged release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants