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

Release v0.17.0 #542

Merged
merged 12 commits into from Jan 10, 2024
Merged

Release v0.17.0 #542

merged 12 commits into from Jan 10, 2024

Conversation

hacdias
Copy link
Member

@hacdias hacdias commented Jan 10, 2024

Sister Kubo PR: ipfs/kubo#10285

hacdias and others added 10 commits December 6, 2023 10:46
From:
```
init github.com/ipfs/boxo/gateway/assets @26 ms, 18 ms clock, 9887320 bytes, 1496 allocs
```
To:
```
init github.com/ipfs/boxo/gateway/assets @10 ms, 3.3 ms clock, 3368 bytes, 11 allocs
```

This is not optimal but better solutions (like lazy loading) require breaking the API and it's a better job for future someone else.
It appears there's a typo in the package name. It should be opentelemetry-go instead of opentelemtry-go.
blockservice is explicitely tolerent to having a nil exchange.
The constructor even logs that as running an offline blockservice.

Everything is tolerent except close, which panics.

It is confusing for consumers to only have to call close based on if it's online or offline.
They could also instead call close directly on the exchange (then we could remove blockservice's Close method).

Anyway here is as a simple fix, add a nil check.
@hacdias hacdias requested a review from a team as a code owner January 10, 2024 15:23
@hacdias hacdias self-assigned this Jan 10, 2024
@hacdias hacdias changed the base branch from main to release January 10, 2024 15:27
@hacdias hacdias requested a review from lidel as a code owner January 10, 2024 15:27
@hacdias hacdias added the release Merging this PR will create a tagged release label Jan 10, 2024
Copy link

codecov bot commented Jan 10, 2024

Codecov Report

Attention: 70 lines in your changes are missing coverage. Please review.

Comparison is base (709c7c6) 65.66% compared to head (ad4e2b2) 65.60%.

Impacted file tree graph

@@             Coverage Diff             @@
##           release     #542      +/-   ##
===========================================
- Coverage    65.66%   65.60%   -0.06%     
===========================================
  Files          207      207              
  Lines        25543    25590      +47     
===========================================
+ Hits         16772    16789      +17     
- Misses        7306     7328      +22     
- Partials      1465     1473       +8     
Files Coverage Δ
...ernal/providerquerymanager/providerquerymanager.go 85.47% <100.00%> (-1.66%) ⬇️
bitswap/client/internal/tracing.go 100.00% <100.00%> (ø)
bitswap/internal/testutil/testutil.go 55.12% <100.00%> (ø)
bitswap/internal/tracing.go 100.00% <100.00%> (ø)
...swap/server/internal/decision/blockstoremanager.go 91.01% <100.00%> (ø)
blockservice/internal/tracing.go 100.00% <100.00%> (ø)
gateway/assets/node.go 55.95% <100.00%> (ø)
gateway/errors.go 83.33% <100.00%> (ø)
gateway/gateway.go 85.03% <100.00%> (ø)
gateway/lazyseek.go 79.41% <100.00%> (ø)
... and 35 more

... and 10 files with indirect coverage changes

Copy link

Suggested version: v0.17.0

Comparing to: v0.16.0 (diff)

Changes in go.mod file(s):

(empty)

gorelease says:

# diagnostics
go.mod: the following requirements are needed
	github.com/cespare/xxhash@v1.1.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.16.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.

@hacdias hacdias merged commit 8530184 into release Jan 10, 2024
17 checks passed
@hacdias hacdias deleted the release-v0.17.0 branch February 20, 2024 08:48
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
Status: 🎉 Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants