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

feat: allow use statements to be marked unstable #3

Merged
merged 2 commits into from
Jun 27, 2024
Merged

Conversation

joshka
Copy link
Member

@joshka joshka commented Jun 27, 2024

This allows the pattern of re-exporting code defined in private modules,
while still requiring the unstable feature to be enabled.

This allows the pattern of re-exporting code defined in private modules,
while still requiring the unstable feature to be enabled.
@codecov-commenter
Copy link

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

@joshka joshka merged commit 40bafe1 into main Jun 27, 2024
11 checks passed
@joshka joshka deleted the jm/use-statments branch June 27, 2024 11:27
@github-actions github-actions bot mentioned this pull request Jun 27, 2024
joshka pushed a commit that referenced this pull request Jun 27, 2024
## 🤖 New release
* `instability`: 0.3.0 -> 0.3.1

<details><summary><i><b>Changelog</b></i></summary><p>

<blockquote>

##
[0.3.1](instability-v0.3.0...instability-v0.3.1)
- 2024-06-27

### Added
- allow use statements to be marked unstable
([#3](#3))

### Other
- tweak doc wording and formatting
([#4](#4))
- add release automation
([#1](#1))
</blockquote>


</p></details>

---
This PR was generated with
[release-plz](https://github.com/MarcoIeni/release-plz/).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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