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:
^1.10.0
->^2.0.0
^1.10.0
->^2.0.0
^2.0.0
->^3.0.0
Release Notes
bufbuild/protobuf-es (@bufbuild/protobuf)
v2.2.3
Compare Source
What's Changed
Full Changelog: bufbuild/protobuf-es@v2.2.2...v2.2.3
v2.2.2
Compare Source
What's Changed
New Contributors
Full Changelog: bufbuild/protobuf-es@v2.2.1...v2.2.2
v2.2.1
Compare Source
What's Changed
Full Changelog: bufbuild/protobuf-es@v2.2.0...v2.2.1
v2.2.0
Compare Source
What's Changed
DescMethod
variants by @srikrsna-buf in https://github.com/bufbuild/protobuf-es/pull/985New Contributors
Full Changelog: bufbuild/protobuf-es@v2.1.0...v2.2.0
v2.1.0
Compare Source
What's Changed
Full Changelog: bufbuild/protobuf-es@v2.0.0...v2.1.0
v2.0.0
Compare Source
What's new in version 2
To support Protobuf editions, we have to make breaking changes that also affect users of proto2 and proto3. This prompted us to make more extensive changes that take feedback from version 1 into account:
We no longer use classes. Instead, we generate a schema object and a type for every message. To create a new instance, to serialize, and for other concerns, we provide functions. Here is a simple example:
If you use proto3, messages are now plain objects. Files with proto2 and editions use the prototype chain to track field presence.
This approach solves several outstanding issues, such as:
Contributors
Thanks to @srikrsna-buf for his contributions to v2!
unjs/unbuild (unbuild)
v3.3.1
Compare Source
compare changes
🩹 Fixes
❤️ Contributors
v3.3.0
Compare Source
compare changes
🚀 Enhancements
inlineDependencies
(#480)🩹 Fixes
💅 Refactors
withTrailingSlash
util (#482)🏡 Chore
❤️ Contributors
v3.2.0
Compare Source
compare changes
🚀 Enhancements
mkdist
errors in creating declarations (#473)🩹 Fixes
.d.cts
default export type (#458)🏡 Chore
❤️ Contributors
v3.1.0
Compare Source
compare changes
🚀 Enhancements
name
,exports
andimports
(#469)production
condition (#470)🩹 Fixes
@types/
fromdevDependencies
(#471)🏡 Chore
❤️ Contributors
v3.0.1
Compare Source
compare changes
🩹 Fixes
🏡 Chore
❤️ Contributors
v3.0.0
Compare Source
See github release notes.
Configuration
📅 Schedule: Branch creation - "on monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.