v0.14.0

⚠️ DO NOT USE THIS RELEASE

Due to publication issues, the new intermediate artefacts for jewel-ui and jewel-foundation described below were not published. Use release 0.14.1, which has no functional changes, but includes the missing artefacts.

What's Changed

• Add support for IJP 24.1 by @rock3r in #290
• Switching to the new branching strategy by @rock3r in #292
• #291 — Fix icons patching and theming issues in 241 by @rock3r in #293
• Add Markdown renderer code and sample by @rock3r in #294
• Add tagRelease task to root by @rock3r in #299

New Markdown renderer

This Jewel milestone introduces a new Markdown renderer. You can test it in the standalone sample:

For more information you can refer to the markdown/README.md file.

Supported IntelliJ Platform versions

IntelliJ Platform version	Git tag	Bridge artifact
2024.1	v0.14.0	jewel-ide-laf-bridge-241
2023.3	v0.14.0-233	jewel-ide-laf-bridge-233
2023.2	v0.14.0-232	jewel-ide-laf-bridge-232

Note:
Starting from this milestone, the various versions of the bridge depend on a distinct set of jewel-foundation and jewel-ui artefacts. This is to accommodate differences in resources, logic, and appearance that are present in different IJP releases.

The bridge for the latest supported version of the IJP will be built from main and will depend on the "base" jewel-foundation and jewel-ui. The bridge artefacts supporting older IJP versions will use the -XXX suffix of those dependencies, where XXX is the major IJP version, like for the bridge artifact itself.

The standalone module will always use the "base" artefacts for jewel-foundation and jewel-ui.

The Markdown renderer will use whatever it finds on the classpath.

---

Don't forget to add the custom Maven repository:

repositories {
    maven("https://packages.jetbrains.team/maven/p/kpm/public")
}

Full Changelog: v0.13.2...v0.14.0