Skip to content

Remove the dead Space repository and add IDE update loop skills - #73

Open
Tsyklop wants to merge 2 commits into
mainfrom
ide-update/2026-11-18
Open

Tsyklop wants to merge 2 commits into
mainfrom
ide-update/2026-11-18

Conversation

@Tsyklop

@Tsyklop Tsyklop commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

Fixes a build break that blocks every artifact not yet in the Gradle cache, and adds Claude Code skills that check for new IDE versions, build against them and report the failures.

Dead JetBrains Space repository

common-conventions.gradle.kts declared https://maven.pkg.jetbrains.space/kotlin/p/kotlin/kotlin-js-wrappers. That host no longer resolves (checked with the local DNS and with 1.1.1.1): JetBrains Space package hosting is shut down. Gradle asks repositories in declaration order, and this one came before the IntelliJ Platform and Marketplace repositories. So every artifact that wasn't cached yet failed on it instead of falling through to the next repository.

It surfaced on 263 at main: the Rust plugin published 263.7307.313, com.jetbrains.rust:latest picked it up, and :intellij-plugin:hs-Rust:compileKotlin failed with Could not GET 'https://maven.pkg.jetbrains.space/...'. Any build against a new IDE version would fail the same way. Builds only kept working because everything they needed was already cached.

The only artifact taken from that repository, kotlin-css-jvm 2026.8.4, is on Maven Central.

IDE update loop skills

Two user-invoked project skills in .claude/skills/:

  • /ide-update-loop checks the IntelliJ Maven repository for newer releases of every supported platform branch. It then builds against them the way CI does (compile, test, verify), sorts the failures into classes and writes a report. It doesn't edit the checkout: the versions reach Gradle as -P overrides, and the evidence goes to build/ide-update-loop/<run>/.
  • /ide-update-fix <items> applies the accepted report items on a branch and rebuilds until the affected platforms are green. Because common code is shared, it then compiles the other platforms. It commits or opens a PR only on request.

The scripts are Python 3 with no dependencies outside the standard library:

  • check_ide_updates.py checks versions.
  • run_build.py runs the build stages.
  • analyze_build.py groups compiler errors, JUnit failures and Plugin Verifier verdicts, labels known flakes and environment problems, and compares a build before and after a fix.
  • diff_platform.py diffs the product-info.json of two IDEs. On the cached 263 EAP → 2026.3 pair it lists the modules that broke the 263 release update (Update 263 IDE versions to the 2026.3 release #71): updateChecker, credentialStore, vcs.core.

reference/platform-breakage.md collects the causes this repo has met during platform updates and how they were fixed. CLAUDE.md gets a pointer to the skills, and .gitignore now ignores local Claude Code worktrees, personal settings and __pycache__.

Current state, as the first run found it: newer releases exist for all five branches (e.g. 262: 2026.2.1 → 2026.2.5; Rider 263: RC1 → 2026.3), and branch 271 has appeared (RD-2027.1-SNAPSHOT). This PR doesn't bump any version.

Testing

Local runs on Windows, at this branch:

  • 263: compile, which failed before the fix, now passes. :intellij-plugin:test :hs-edu-format:test :hs-framework-storage:test ran 722 of 723 tests green. The one failure was PluginLoadingTest, in setUp with index Stubs has status REQUIRES_REBUILD. The set of plugins in the test sandbox had changed, which left a stale index, and a rerun passed. verifyPlugin reports Compatible.
  • 252, 253, 261, 262: compile (testClasses of all modules) passes. Tests and verify weren't run there; CI covers 261 and 262.
  • Scripts: checked against the live Maven metadata, the cached IDEs and real build logs.

Not covered: com.jetbrains.rust:latest resolves the -windows-arm64 build of 263.7307.313 on an x64 machine. Compilation doesn't care, but the plugin's native parts would be the wrong architecture in runIde. That's a separate follow-up.

maven.pkg.jetbrains.space no longer resolves: JetBrains Space package
hosting is shut down. Gradle asks repositories in declaration order, and
this one came before the IntelliJ Platform and Marketplace repositories,
so every artifact that was not cached yet failed on it instead of falling
through to the next repository. The new Rust plugin build for 263
(263.7307.313) broke `:intellij-plugin:hs-Rust:compileKotlin` this way,
and any build against a new IDE version would too.

The only artifact taken from it, kotlin-css-jvm 2026.8.4, is on Maven
Central.
Two user-invoked project skills turn updating the IDE versions in
gradle-<env>.properties into a repeatable loop:

- /ide-update-loop checks the IntelliJ Maven repository for newer
  releases of every supported platform branch, builds the plugin against
  them the way CI does (compile, test, verify), classifies the failures
  and writes a report. It edits nothing: the versions reach Gradle as -P
  overrides and all evidence goes to build/ide-update-loop/<run>/.
- /ide-update-fix applies the items accepted from that report on a
  branch and rebuilds until the affected platforms are green, then
  compiles the other platforms because common code is shared.

The scripts (Python 3, standard library) check versions, run the build
stages, analyze logs and JUnit/Plugin Verifier output, and diff the
product-info.json of two IDEs to predict classes that moved out of the
core classpath. reference/platform-breakage.md collects the causes this
repo has met during platform updates and how they were fixed.

.gitignore now ignores local Claude Code worktrees, personal settings
and Python bytecode, so .claude/skills can be committed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant