Update dependency org.antlr:antlr4 to v4.13.1 #16
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/org.antlr-antlr4-4.x
branch
from
4d13c31
to
f6074f4
Compare
renovate
bot
force-pushed
the
renovate/org.antlr-antlr4-4.x
branch
from
f6074f4
to
d6d083a
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/org.antlr-antlr4-4.x
branch
from
d6d083a
to
301c087
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/org.antlr-antlr4-4.x
branch
from
301c087
to
ff9aae9
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/org.antlr-antlr4-4.x
branch
from
ff9aae9
to
17e0337
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/org.antlr-antlr4-4.x
branch
from
17e0337
to
c663a37
Compare
renovate
bot
force-pushed
the
renovate/org.antlr-antlr4-4.x
branch
from
c663a37
to
38b76c9
Compare
renovate
bot
changed the title
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:
4.9.2->4.13.1Release Notes
antlr/antlr4 (org.antlr:antlr4)
v4.13.1Compare Source
Pull requests grouped by target
csharp target
go target
java target
this-escapewarning introduced in JDK 21. (actions, target:java)javascript target
swift target
dart target
Contributors
v4.13.0Compare Source
This is primarily change to the Go target itself and its release location, which has moved to https://github.com/antlr4-go/antlr. The code still lives and this repository, but for release purposes we've created a new organization and repository so that Go users can pull versions down according to the repository and label rules
Issues fixed
Improvements, features
Pull requests grouped by target
csharp target
cpp target
go target
javascript target
python3 target
PEP 621-compliantpyproject.toml. (comp:build, target:python3)Contributors
v4.12.0Compare Source
The 4.12.0 release is primarily about the new TypeScript target created by @ericvergnaud. There are also a number of fixes to the various targets, as you can see from the descriptions below.
Issues fixed
Improvements, features
Pull requests grouped by target
csharp target
cpp target
go target
java target
javascript target
python2 target
python3 target
swift target
php target
dart target
Contributors
v4.11.1: (just fixes 4.11.0 release issue)Compare Source
Just fixes 4.11.0 release issue. I forgot to change runtime tool version so it didn't say SNAPSHOT.
v4.11.0Compare Source
4.11.0 consist primarily:
The details by type and target follow.
Issues fixed
Improvements, features
Pull requests grouped by target
csharp target
cpp target
go target
java target
@SuppressWarnings("CheckReturnValue")to prevent error_prone lib errors. (target:java)javascript target
python2 target
python3 target
swift target
php target
dart target
Contributors
v4.10.1Compare Source
Tiny update to fix build issue where java requirement for runtime was 11 not 1.8.
What's Changed
Full Changelog: antlr/antlr4@v4.10.0...4.10.1
v4.10: Major feature, code clean up, and bug fix releaseCompare Source
ANTLR version 4.10
This is a very major release with a number of important changes. There have been many valuable contributions, but I welcome @KvanTTT and @jcking as recent "official" major ANTLR contributors. :)
WARNING: Generated 4.10 lexers and parsers are incompatible with code generated by previous versions of ANTLR. You must regenerate all of your code from grammars to use the new runtime. This is true of all targets (except probably javascript).
Repo branching structure
We have changed the branching structure of the repository. The default branch for this repo remains
masterand it is the latest stable release with tags for the various releases; e.g., see release tag 4.9.3. We now do development work in branchdevbetween releases and all pull requests should be derived from that branch. Thedevbranch is merged back intomasterto cut a release and the release state is tagged (e.g., with4.10-rc.1or4.10.) Visually our process looks roughly like this:Targets such as Go that pull directly from the repository can use the default
masterbranch but can also pull from the activedevbranch:Developers certificate of origin
In order to bring ANTLR more in line with current standard standards for contribution processes, as of 4.10, ANTLR uses the Linux Foundation's Developer Certificate of Origin, DCO, version 1.1. See file https://github.com/antlr/antlr4/raw/master/developer-cert-of-origin.txt . It is simpler than the original contributors license agreement, which required programmers to sign the
contributors.txtfile, which has now moved to file historical-contributors-agreement.txt .Each commit in pull requests must have a "signature", which is simple as using
-s(not-S) on the git commit command:Github's pull request process enforces the sig and gives instructions on how to fix any commits that lack the sig. See https://github.com/apps/dco for more info.
4.10-generated parsers incompatible with previous runtimes
ANTLR not only generates recursive-descent parsers; it generates a state machine called an augmented transition network (ATN) in serialized form as a bunch of integers stored in the generated parser and lexer files. This serialization format was changed for 4.10 to remove a size limit on the supported ATNs. See https://github.com/antlr/antlr4/pull/3591.
The key point here is that we changed the version number stored inside the serialization format and so, in order to use this new version of ANTLR, you must regenerate all of your lexers and parsers using the 4.10 tool and then use the new runtime. Parsers generated with 4.10 or not compatible with previous versions of the runtime.
Increasing minimum java version
Going forward, we are using Java 11 for the source code and the compiled .class files for the ANTLR tool. The Java runtime target, however, and the associated runtime tests use Java 8 (bumping up from Java 7).
JavaScript target
The JS target has been substantially reworked.
Miscellaneous improvements
caseInsensitiveoption now.Changes report
The following report is generated by
scripts/github_release_notes.py.Issues fixed
Improvements, features
Pull requests grouped by target
csharp target
cpp target
go target
java target
javascript target
python2 target
python3 target
swift target
AnyObjectinstead ofclass. (target:swift)php target
dart target
latemodifier for Dart generated context classes (target:dart)Contributors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.