Commit Graph

26 Commits

Author SHA1 Message Date
github-actions[bot] a39f132b91 Update versions to 1.19.0-SNAPSHOT and 1.19.0-beta29-SNAPSHOT 2026-07-17 13:42:56 +00:00
github-actions[bot] 66ad5ee6d5 Release versions 1.18.0 and 1.18.0-beta28 2026-07-17 12:34:45 +00:00
github-actions[bot] 7d7c3349d7 Update versions to 1.18.0-SNAPSHOT and 1.18.0-beta28-SNAPSHOT 2026-06-26 14:49:40 +00:00
github-actions[bot] 207407aec9 Release versions 1.17.0 and 1.17.0-beta27 2026-06-26 13:13:06 +00:00
Eunbin Son 6020c8a1ce
fix: Decode Markdown as UTF-8 instead of the platform default charset (#5436)
## Issue
Closes #5435
<!-- Replace # with the real issue number before submitting. -->

## Change

`MarkdownDocumentParser.parse()` decoded input via `new
InputStreamReader(inputStream)` — the JVM platform default charset —
silently corrupting non-ASCII Markdown on non-UTF-8 platforms.

- Pass an explicit `UTF_8` to `InputStreamReader`, matching
`TextDocumentParser` (UTF-8 default) and `YamlDocumentParser` (UTF-8
internally); other parsers in this module decode via backends and are
unaffected.
- Test: a multibyte (café / 한글 / emoji) UTF-8 round-trip. The
platform-default regression is not unit-testable —
`Charset.defaultCharset()` is fixed at JVM start (UTF-8 on CI) — so this
is positive coverage.


## General checklist
- [X] There are no breaking changes (API, behaviour) <!-- no API change;
the only behaviour change is the bug fix (platform-default → UTF-8), a
no-op where default is already UTF-8 -->
- [X] I have added unit and/or integration tests for my change
- [ ] The tests cover both positive and negative cases <!-- positive
coverage only; the platform-default regression is not unit-testable
without JVM-level charset flags -->
- [X] I have manually run all the unit and integration tests in the
module I have added/changed, and they are all green
- [ ] I have manually run all the unit and integration tests in the core
and main modules, and they are all green <!-- N/A — only the changed
module was run locally; CI covers core+main -->
- [ ] I have added/updated the documentation <!-- N/A — no public API or
behaviour change requiring docs -->
- [ ] I have added an example in the examples repo (only for "big"
features) <!-- N/A — minor bug fix -->
- [ ] I have added/updated Spring Boot starter(s) (if applicable) <!--
N/A — no starter changes needed -->
2026-06-17 18:16:06 +02:00
github-actions[bot] 01de41d641 Update versions to 1.17.0-SNAPSHOT and 1.17.0-beta27-SNAPSHOT 2026-06-06 06:46:38 +00:00
github-actions[bot] cd836845dd Release versions 1.16.0 and 1.16.0-beta26 2026-06-05 15:46:56 +00:00
github-actions[bot] 6185599e37 Update versions to 1.16.0-SNAPSHOT and 1.16.0-beta26-SNAPSHOT 2026-05-15 16:21:14 +00:00
github-actions[bot] d0e54aa006 Release versions 1.15.0 and 1.15.0-beta25 2026-05-15 15:55:12 +00:00
renovate[bot] 006aeefda9
fix(deps): update commonmark.version to v0.28.0 (#5232)
This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
|
[org.commonmark:commonmark](https://redirect.github.com/commonmark/commonmark-java)
| `0.26.0` → `0.28.0` |
![age](https://developer.mend.io/api/mc/badges/age/maven/org.commonmark:commonmark/0.28.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/org.commonmark:commonmark/0.26.0/0.28.0?slim=true)
|
|
[org.commonmark:commonmark-ext-yaml-front-matter](https://redirect.github.com/commonmark/commonmark-java)
| `0.26.0` → `0.28.0` |
![age](https://developer.mend.io/api/mc/badges/age/maven/org.commonmark:commonmark-ext-yaml-front-matter/0.28.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/org.commonmark:commonmark-ext-yaml-front-matter/0.26.0/0.28.0?slim=true)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the [Dependency
Dashboard](../issues/2069) for more information.

---

### Release Notes

<details>
<summary>commonmark/commonmark-java
(org.commonmark:commonmark)</summary>

###
[`v0.28.0`](https://redirect.github.com/commonmark/commonmark-java/blob/HEAD/CHANGELOG.md#0280---2026-03-31)

##### Added

- New extension for alerts (aka callouts/admonitions)
  - Syntax:
    ```
    > [!NOTE]
    > The text of the note.
    ```
- As types you can use NOTE, TIP, IMPORTANT, WARNING, CAUTION; or
configure the
    extension to add additional ones.
- Use class `AlertsExtension` in artifact `commonmark-ext-gfm-alerts`
([#&#8203;420](https://redirect.github.com/commonmark/commonmark-java/issues/420))
- New option `maxOpenBlockParsers` for `Parser.Builder` to set an
overall limit
for the depth of block parsing. If set, any nesting beyond the limit
will be
  parsed as paragraph text instead. The default remains unlimited.

###
[`v0.27.1`](https://redirect.github.com/commonmark/commonmark-java/blob/HEAD/CHANGELOG.md#0271---2026-01-14)

##### Fixed

- Line(s) after a hard line break would sometimes also get an unwanted
hard
line break, e.g. if they ended in emphasis or other non-text inlines
([#&#8203;415](https://redirect.github.com/commonmark/commonmark-java/issues/415))
- `TextContentRenderer` (for plain text): Fix nested lists on the same
line
([#&#8203;413](https://redirect.github.com/commonmark/commonmark-java/issues/413))
- Fix minor performance regression with pathological input (deeply
nested
  brackets) that was introduced in version 0.23.0.

###
[`v0.27.0`](https://redirect.github.com/commonmark/commonmark-java/blob/HEAD/CHANGELOG.md#0270---2025-10-12)

##### Added

- Autolink extension: Now supports configuration of different link types
that
should be recognized and converted to links. See
`AutolinkExtension#builder`

| Type | Default? | Description |
| ------- | -------- |
------------------------------------------------------ |
| `URL` | Yes | URL with a protocol such as `https://example.com` |
| `EMAIL` | Yes | Email address such as `foo@example.com` |
| `WWW` | Yes | Address beginning with `www` such as `www.example.com` |

Note that this changes the behavior of `AutolinkExtension.create()` to
now also
include `WWW` links by default. To re-enable the previous behavior, use:

  ```java
AutolinkExtension.builder().linkTypes(AutolinkType.URL,
AutolinkType.EMAIL).build();
  ```

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- 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 these
updates again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/langchain4j/langchain4j).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNzMuNiIsInVwZGF0ZWRJblZlciI6IjQzLjE3My42IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-05-14 12:59:23 +02:00
github-actions[bot] 628ac34c01 Update versions to 1.15.0-SNAPSHOT and 1.15.0-beta25-SNAPSHOT 2026-04-30 18:43:12 +00:00
github-actions[bot] 4917afa297 Release versions 1.14.0 and 1.14.0-beta24 2026-04-30 18:10:30 +00:00
github-actions[bot] 4798a89d66 Update versions to 1.14.0-SNAPSHOT and 1.14.0-beta24-SNAPSHOT 2026-04-09 14:41:27 +00:00
github-actions[bot] 759cd9a236 Release versions 1.13.0 and 1.13.0-beta23 2026-04-09 13:07:30 +00:00
Dmytro Liubarskyi e10abf04d0
Update versions to 1.13.0-SNAPSHOT and 1.13.0-beta23-SNAPSHOT (#4710)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2026-03-13 11:39:50 +01:00
Dmytro Liubarskyi c92ea033e4
Update versions to 1.13.0-SNAPSHOT and 1.13.0-beta22-SNAPSHOT (#4666)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2026-03-05 17:18:22 +01:00
Dmytro Liubarskyi 336b2accce
Update versions to 1.12.0-SNAPSHOT and 1.12.0-beta20-SNAPSHOT (#4537)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2026-02-04 14:27:44 +01:00
Dmytro Liubarskyi 778be1b360
Update versions to 1.11.0-SNAPSHOT and 1.11.0-beta19-SNAPSHOT (#4285)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2025-12-24 15:38:05 +01:00
Dmytro Liubarskyi 0098aca4d0 fixed missing transitive dependency 2025-12-10 09:50:39 +01:00
Dmytro Liubarskyi ca6097e35d
Update versions to 1.10.0-SNAPSHOT and 1.10.0-beta18-SNAPSHOT (#4152)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2025-11-28 12:21:30 +01:00
Dmytro Liubarskyi bc0801a4df
Update versions to 1.10.0-SNAPSHOT and 1.10.0-beta17-SNAPSHOT (#4140)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2025-11-26 17:38:36 +01:00
Dmytro Liubarskyi a473835133
Update versions to 1.9.0-SNAPSHOT and 1.9.0-beta16-SNAPSHOT (#3951)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2025-10-24 16:51:33 +02:00
Xin Wang b56a3183c4
Fix markdown tests package (#3844)
<!--
Thank you so much for your contribution!

Please fill in all the sections below.
Please open the PR as a draft initially. Once it is reviewed and
approved, we will ask you to add documentation and examples.
Please note that PRs with breaking changes or without tests will be
rejected.

Please note that PRs will be reviewed based on the priority of the
issues they address.
We ask for your patience. We are doing our best to review your PR as
quickly as possible.
Please refrain from pinging and asking when it will be reviewed. Thank
you for understanding!
-->

## Issue
<!-- Please specify the ID of the issue this PR is addressing. For
example: "Closes #1234" or "Fixes #1234" -->
Closes #

## Change
<!-- Please describe the changes you made. -->
fix markdown tests package

## General checklist
<!-- Please double-check the following points and mark them like this:
[X] -->
- [ ] There are no breaking changes (API, behaviour)
- [ ] I have added unit and/or integration tests for my change
- [ ] The tests cover both positive and negative cases
- [ ] I have manually run all the unit and integration tests in the
module I have added/changed, and they are all green
- [ ] I have manually run all the unit and integration tests in the
[core](https://github.com/langchain4j/langchain4j/tree/main/langchain4j-core)
and
[main](https://github.com/langchain4j/langchain4j/tree/main/langchain4j)
modules, and they are all green
<!-- Before adding documentation and example(s) (below), please wait
until the PR is reviewed and approved. -->
- [ ] I have added/updated the
[documentation](https://github.com/langchain4j/langchain4j/tree/main/docs/docs)
- [ ] I have added an example in the [examples
repo](https://github.com/langchain4j/langchain4j-examples) (only for
"big" features)
- [ ] I have added/updated [Spring Boot
starter(s)](https://github.com/langchain4j/langchain4j-spring) (if
applicable)


## Checklist for adding new maven module
<!-- Please double-check the following points and mark them like this:
[X] -->
- [ ] I have added my new module in the root `pom.xml` and
`langchain4j-bom/pom.xml`


## Checklist for adding new embedding store integration
<!-- Please double-check the following points and mark them like this:
[X] -->
- [ ] I have added a `{NameOfIntegration}EmbeddingStoreIT` that extends
from either `EmbeddingStoreIT` or `EmbeddingStoreWithFilteringIT`
- [ ] I have added a `{NameOfIntegration}EmbeddingStoreRemovalIT` that
extends from `EmbeddingStoreWithRemovalIT`

## Checklist for changing existing embedding store integration
<!-- Please double-check the following points and mark them like this:
[X] -->
- [ ] I have manually verified that the
`{NameOfIntegration}EmbeddingStore` works correctly with the data
persisted using the latest released version of LangChain4j
2025-10-10 10:07:53 +02:00
Dmytro Liubarskyi 34632c06a2 nex dev iteration 2025-10-02 17:17:35 +02:00
Dmytro Liubarskyi 7add1a1b4e next dev iteration 2025-09-26 16:54:16 +02:00
Xin Wang 63f4e02c53
Introduce markdown document parser (#3732)
<!--
Thank you so much for your contribution!

Please fill in all the sections below.
Please open the PR as a draft initially. Once it is reviewed and
approved, we will ask you to add documentation and examples.
Please note that PRs with breaking changes or without tests will be
rejected.

Please note that PRs will be reviewed based on the priority of the
issues they address.
We ask for your patience. We are doing our best to review your PR as
quickly as possible.
Please refrain from pinging and asking when it will be reviewed. Thank
you for understanding!
-->

## Issue
<!-- Please specify the ID of the issue this PR is addressing. For
example: "Closes #1234" or "Fixes #1234" -->
Closes #

## Change
<!-- Please describe the changes you made. -->
Introduce markdown document parser.

## General checklist
<!-- Please double-check the following points and mark them like this:
[X] -->
- [x] There are no breaking changes
- [x] I have added unit and/or integration tests for my change
- [x] The tests cover both positive and negative cases
- [x] I have manually run all the unit and integration tests in the
module I have added/changed, and they are all green
- [x] I have manually run all the unit and integration tests in the
[core](https://github.com/langchain4j/langchain4j/tree/main/langchain4j-core)
and
[main](https://github.com/langchain4j/langchain4j/tree/main/langchain4j)
modules, and they are all green
<!-- Before adding documentation and example(s) (below), please wait
until the PR is reviewed and approved. -->
- [x] I have added/updated the
[documentation](https://github.com/langchain4j/langchain4j/tree/main/docs/docs)
- [ ] I have added an example in the [examples
repo](https://github.com/langchain4j/langchain4j-examples) (only for
"big" features)
- [ ] I have added/updated [Spring Boot
starter(s)](https://github.com/langchain4j/langchain4j-spring) (if
applicable)


## Checklist for adding new maven module
<!-- Please double-check the following points and mark them like this:
[X] -->
- [x] I have added my new module in the root `pom.xml` and
`langchain4j-bom/pom.xml`


## Checklist for adding new embedding store integration
<!-- Please double-check the following points and mark them like this:
[X] -->
- [ ] I have added a `{NameOfIntegration}EmbeddingStoreIT` that extends
from either `EmbeddingStoreIT` or `EmbeddingStoreWithFilteringIT`
- [ ] I have added a `{NameOfIntegration}EmbeddingStoreRemovalIT` that
extends from `EmbeddingStoreWithRemovalIT`

## Checklist for changing existing embedding store integration
<!-- Please double-check the following points and mark them like this:
[X] -->
- [ ] I have manually verified that the
`{NameOfIntegration}EmbeddingStore` works correctly with the data
persisted using the latest released version of LangChain4j
2025-09-24 16:44:43 +02:00