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.10.0 #1406

Merged
merged 1 commit into from
Nov 14, 2022
Merged

release: v0.10.0 #1406

merged 1 commit into from
Nov 14, 2022

Conversation

EverlastingBugstopper
Copy link
Contributor

@EverlastingBugstopper EverlastingBugstopper commented Nov 10, 2022

[0.10.0] - 2022-11-10

Important: 1 potentially breaking change below, indicated by ❗ BREAKING ❗

❗ BREAKING ❗

  • Fix implementation of --header argument - @EverlastingBugstopper, chore: fix implementation of header option #1369 fixes Introspect documentation is incorrect #1365

    This change tightens up usage of the --header argument used for introspect commands by disallowing previously valid (but undocumented) usage like this: --header "Header-1: value" "Header-2: value". After this change, you must conform to what we have in the documentation, which indicates separate instances of the --header argument for each header, like so: --header "Header-1: value" --header "Header-2: value".

🚀 Features

🛠 Maintenance

📚 Documentation

@EverlastingBugstopper
Copy link
Contributor Author

EverlastingBugstopper commented Nov 10, 2022

This is a draft PR until tomorrow Monday when I plan on walking through the release with @gocamille.

We also need to merge these two PRs and add them to the changelog

@EverlastingBugstopper
Copy link
Contributor Author

FYI for folks watching this - the plan is to release this on Monday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment