Skip to content

Update ex_doc 0.24.2 → 0.40.3 (major) - #65

Closed
depfu[bot] wants to merge 1 commit into
mainfrom
depfu/update/elixir/ex_doc-0.40.3
Closed

Update ex_doc 0.24.2 → 0.40.3 (major)#65
depfu[bot] wants to merge 1 commit into
mainfrom
depfu/update/elixir/ex_doc-0.40.3

Conversation

@depfu

@depfu depfu Bot commented Jul 26, 2026

Copy link
Copy Markdown

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ ex_doc (0.24.2 → 0.40.3) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ earmark_parser (indirect, 1.4.13 → 1.4.46) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ makeup (indirect, 1.0.5 → 1.2.2) · Repo · Changelog

Release Notes

1.2.2 (from changelog)

Escape group ids when generating HTML.

1.2.1 (from changelog)

Allow empty middle on string_like combinators.

1.2.0 (from changelog)

Make reparsing at end of string configurable.

1.1.2 (from changelog)

Do not attempt reparsing if surrounded by reaches end of string.

1.1.1 (from changelog)

Add dracula theme.

Add one dark theme.

Fix warnings on recent Elixir versions.

1.1.0 (from changelog)

Require NimbleParsec ~> 1.2.2 onwards to prepare for future deprecations.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 6 commits:

↗️ makeup_elixir (indirect, 0.15.1 → 1.0.1) · Repo · Changelog

Release Notes

1.0.1 (from changelog)

  • Support multi-letter sigils
  • Allow options to be registered with custom lexers

1.0.0 (from changelog)

  • Allow registering custom sigils
  • Allow node names in prompts
  • Allow \t and \f as whitespace

0.16.1 (from changelog)

  • Relax NimbleParsec dependency

0.15.2 (from changelog)

  • Highlight Erlang calls as modules.
  • Support digits as modifiers in sigils.
  • Support stepped ranges operators ..//.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 5 commits:

↗️ makeup_erlang (indirect, 0.1.1 → 1.1.0) · Repo · Changelog

Release Notes

1.1.0 (from changelog)

Added

  • Support for OTP 27+ triple-, quadruple-, and quintuple-quoted strings, including the matching sigil delimiters.
  • Support for OTP 27 underscore separators in numeric literals (1_000_000, 16#FF_FF, 0.1_5e1_0).
  • Support for OTP 25/27 ?= maybe-match operator as a single token.
  • Support for OTP 29 native records, including the external #Module:Name{...} / #Module:Name.field forms and variable-shape / keyword record names (#State{}, #case{}, #fun{}).
  • Distinct token for parameterised macro calls (?FOO(args) → :name_function) versus parameterless macro references (?FOO → :name_constant).
  • :string_escape sub-tokens emitted inside plain double-quoted strings (previously only emitted inside triple-quoted strings).
  • Multi-character escape sequences ($\xFF, $\x{1F600}, $\077, $\^A) in $\... character literals tokenised as a single escape.
  • Underscore-prefixed identifiers (_5, _X, _unused) lex as a single :name variable rather than _ + integer/name.

Changed

  • BIF list is now generated at compile time from erl_internal:bif/2, keeping the recognised builtins in sync with the OTP version makeup_erlang is compiled against. Adds 30+ post-OTP-19 BIFs and fixes one stale typo. Closes #13.
  • Reserved words written adjacent to ( (e.g. fun(X)) are recovered as :keyword instead of misclassified :name_function.
  • Erlang shell prompts (1> ...) are detected after multi-line whitespace blocks, not only after a single immediate \n.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 48 commits:

↗️ nimble_parsec (indirect, 1.1.0 → 1.4.2) · Repo · Changelog

Release Notes

1.4.2 (from changelog)

Enhancements

  • Remove more warnings on Elixir v1.18+

1.4.1 (from changelog)

Enhancements

  • Remove warnings on Elixir v1.18+

1.4.0 (from changelog)

Enhancements

  • Remove warnings and require Elixir v1.12

1.3.1 (from changelog)

Bug fixes

  • Make error messages consistent across Elixir versions
  • Ensure integer(max: ...) also sets a minimum of 1
  • Do not lose context on repeat_while

1.3.0 (from changelog)

Deprecations

  • Deprecate returning a {acc, context} from quoted_post_traverse and quoted_pre_traverse. Return {rest, acc, context} instead.

Bug fixes

  • Avoid compile warnings with negative lookahead
  • Fix clause warning for integer combinator

1.2.2 (from changelog)

Enhancements

  • Allow rest to be returned from post_traverse/pre_traverse

1.2.1 (from changelog)

Bug fixes

  • Improve typespecs

1.2.0 (from changelog)

Enhancements

  • Add generator support to NimbleParsec: it now generates code that matches a combinator

Bug fixes

  • Fix using eventually with constructs that can accumulate
  • Fix lookahead combinators running in reverse order
  • Raise on invalid min for integer

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 63 commits:

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu Bot added the depfu label Jul 26, 2026
@depfu depfu Bot mentioned this pull request Jul 26, 2026
Closed
@depfu

depfu Bot commented Sep 4, 2026

Copy link
Copy Markdown
Author

Closed in favor of #67.

@depfu depfu Bot closed this Sep 4, 2026
@depfu
depfu Bot deleted the depfu/update/elixir/ex_doc-0.40.3 branch September 4, 2026 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants