unkeyed / unkey

Open source API management platform
https://go.unkey.com
Other
2.53k stars 242 forks source link

fix stream formatting #1810

Closed domeccleston closed 1 week ago

domeccleston commented 1 week ago

Huly®: ENG-1804

vercel[bot] commented 1 week ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 26, 2024 2:16pm
planetfall ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 26, 2024 2:16pm
play ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 26, 2024 2:16pm
workflows 🔄 Building (Inspect) Visit Preview 💬 Add feedback Jun 26, 2024 2:16pm
www 🔄 Building (Inspect) Visit Preview 💬 Add feedback Jun 26, 2024 2:16pm
changeset-bot[bot] commented 1 week ago

⚠️ No Changeset found

Latest commit: 791604daafef48f7b83edf88a6fa8e56f78bd2ff

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

github-actions[bot] commented 1 week ago

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Here is an example:

<type>[optional scope]: <description>
fix: I fixed something for Unkey

Details:

No release type found in pull request title "fix stream formatting". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit