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

fix(composition-engine): incorrect import from core/status-codes #426

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

ItMaga
Copy link
Member

@ItMaga ItMaga commented Jul 2, 2024

No description provided.

@ItMaga ItMaga changed the title fix: incorrect import from core/status-codes fix(composition-engine): incorrect import from core/status-codes Jul 2, 2024
@ItMaga ItMaga merged commit 1e91462 into v4-rc Jul 2, 2024
4 of 5 checks passed
@ItMaga ItMaga deleted the itmaga/composition-engine-status-codes-v4 branch July 2, 2024 09:14
bonkalol added a commit that referenced this pull request Jul 29, 2024
* chore: add v4-rc to on: CI rules

* feat: allow specifying custom no content statuses

* test: custom empty body statuses

* chore: fix eslint

* fix: pass noContentStatuses where needed

* chore: improve test name

* 🆙 lib

* chore: improve types near Array.concat()

* chore: explicitly handle all cases in statusesContainStatus()

* 🆙 lib

* chore: update docs about new option `noContentStatuses`

* chore: add a TODO about noContentStatusCodes

* chore: update changelogs

* 🆙 lib

* chore: up version to 4.0.0-rc.38

* [v4] Composition engine (#404)

* 🆙 4.0.0-alpha.39

* Fix bad changelog

* fix(composition-engine): incorrect import from `core/status-codes` (#426)

* 🆙 4.0.0-alpha.40

* Publish package as public access

* Use npm publish instead of yarn npm publish

* Add step to build standalone before publish

* Bump version to test CI

---------

Co-authored-by: Mikhail Kormanovskii <[email protected]>
Co-authored-by: Magomed Chemurziev <[email protected]>
Co-authored-by: Magomed Chemurziev <[email protected]>
Co-authored-by: Abdelrahman Aly Abounegm <[email protected]>
Co-authored-by: Abdelrahman Abounegm <[email protected]>
Co-authored-by: kholstinin <[email protected]>
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