Open
Conversation
122b894 to
d6bfc95
Compare
d6bfc95 to
7cb376b
Compare
7cb376b to
32b64b9
Compare
32b64b9 to
3299866
Compare
3299866 to
ca6ec2c
Compare
3a92f41 to
3a091f2
Compare
3a091f2 to
ceee913
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.28.6→7.29.07.28.6→7.29.24.2.13→4.3.17.16.1→7.19.23.47.0→3.49.0v2.14.0→v2.15.28.5.0→8.6.04.4.1→4.4.33.6.1→3.6.23.92.5→3.94.24.0.0→4.0.211.1.1→11.2.06.6.4→6.7.212.5.2→12.5.312.5.8→12.5.142.3.2→2.3.91.15.6→1.15.78.0.0→8.0.68.0.3→8.0.48.0.3→8.0.78.0.3→8.0.78.0.0→8.0.68.0.3→8.0.78.0.0→8.0.78.0.0→8.0.48.0.0→8.0.48.0.0→8.0.48.0.3→8.0.68.0.3→8.0.78.0.3→8.0.78.0.3→8.0.78.0.3→8.0.78.0.3→8.0.78.0.1→8.0.61.65.1→1.67.08.0.0→8.0.78.0.3→8.0.48.0.3→8.0.78.0.3→8.0.68.0.0→8.0.68.0.3→8.0.48.0.3→8.0.68.0.3→8.0.78.0.1→8.0.68.0.3→8.0.68.0.3→8.0.78.0.3→8.0.48.0.0→8.0.48.0.3→8.0.78.0.3→8.0.68.0.0→8.0.48.0.3→8.0.78.0.1→8.0.63.22.2→3.24.03.22.1→3.24.03.22.1→3.24.03.22.2→3.24.05.104.1→5.105.44.12.0→4.13.02.8.5→2.9.2Release Notes
babel/babel (@babel/core)
v7.29.0Compare Source
v7.29.0 (2026-01-31)
Thanks @simbahax for your first PR!
🚀 New Feature
babel-typesbabel-standalone🐛 Bug Fix
babel-parserextendsclause (@nicolo-ribaudo)babel-traversebabel-plugin-transform-block-scoping,babel-traverse🏃♀️ Performance
babel-generator,babel-runtime-corejs3Committers: 6
api-platform/core (api-platform/core)
v4.3.1Compare Source
What's Changed
New Contributors
Full Changelog: api-platform/core@v4.3.0...v4.3.1
v4.3.0Compare Source
Features
SkipAutoconfigureattribute (#7467)Bug fixes
Breaking changes
@typewithoutputanditemUriTemplate: When usingoutputwithitemUriTemplateon a collection operation, the JSON-LD@typenow uses the resource class name instead of the output DTO class name for semantic consistency withitemUriTemplatebehavior. Update any client code that relies on the DTO class name in@type.property(#7681): Doctrine parameter-based filters (ExactFilter,IriFilter,PartialSearchFilter,UuidFilter) now throwInvalidArgumentExceptionif thepropertyattribute is missing. If you have filter parameters without an explicitproperty, you must either add one or use the:propertyplaceholder in your parameter name.$classMetadata->markReadOnly()) will no longer expose PUT and PATCH operations. Clients sending PUT/PATCH to these resources will receive a 404. If you need write operations on readonly entities, explicitly define them in yourApiResourceattribute.Behavioral changes
@idnow always uses#ShortName(#7771): Hydra documentation classes now consistently use#ShortNameas their@idinstead of schema.org type URIs (e.g.schema:Product). This resolves class identifier collisions when multiple resources shared the same semantic type, which previously caused api-doc-parser conflation. Semantic types configured viatypesare now exposed throughrdfs:subClassOf. Clients should expect class@idand property range changes in the Hydra documentation if resources had customtypesconfigured.isGrantedevaluated before provider (#7500): Security expressions are now evaluated before the state provider runs. Expressions that do not reference theobjectvariable will be checked earlier (at thepre_readstage), improving security by preventing unnecessary database queries on unauthorized requests. Expressions that referenceobjectstill wait for the provider to resolve the entity. Review any security expressions that relied on provider side-effects running before authorization.AllowandAccept-Postheaders per the Linked Data Platform specification. These are informational headers that help clients discover API capabilities and should not break existing integrations.?ui=scalar. To disable it, setenable_scalar: falsein your API Platform configuration.v4.2.22Compare Source
What's Changed
New Contributors
Full Changelog: api-platform/core@v4.2.21...v4.2.22
v4.2.21Compare Source
Bug fixes
v4.2.20Compare Source
Bug fixes
v4.2.19Compare Source
Bug fixes
v4.2.18Compare Source
Bug fixes
v4.2.17Compare Source
Bug fixes
v4.2.16Compare Source
Bug fixes
[
v4.2.15](https://redirect.github.com/api-platfo