Skip to content

chore: prepare to release exn-anyhow#51

Merged
andylokandy merged 1 commit intofast:mainfrom
andylokandy:dev-11
Mar 31, 2026
Merged

chore: prepare to release exn-anyhow#51
andylokandy merged 1 commit intofast:mainfrom
andylokandy:dev-11

Conversation

@andylokandy
Copy link
Copy Markdown
Contributor

No description provided.

exn = { path = "exn" }
exn-anyhow = { path = "exn-anyhow" }
exn = { version = "0.3.0", path = "exn" }
exn-anyhow = { version = "0.1.0", path = "exn-anyhow" }
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tisonkun Will it be better if we align the version of this two crates?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It depends on our breaking change expectation.

I think we typically avoid breaking change in exn so use a separate version would be fine. The exn-anyhow is a thin wrapper over exn and only depends on exn's almost stable API.

So we'd only release exn-anyhow 0.2 when exn 0.4 is out. This should be similar to our strategy to fastrace and fastrace-reqwest.

@andylokandy andylokandy merged commit 534fda1 into fast:main Mar 31, 2026
12 checks passed
@andylokandy andylokandy deleted the dev-11 branch March 31, 2026 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants