<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Business on Ilscipio - Enterprise Commerce Experts</title>
    <link>https://www.ilscipio.com/en/categories/business/</link>
    <description>Recent content in Business on Ilscipio - Enterprise Commerce Experts</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 22 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.ilscipio.com/en/categories/business/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Maintaining 22 Plugins Involves</title>
      <link>https://www.ilscipio.com/en/blog/maintaining-22-plugins-cost/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.ilscipio.com/en/blog/maintaining-22-plugins-cost/</guid>
      <description>&lt;p&gt;JetBrains released 2026.2 and I had 22 compatibility matrices to update. That is 22 plugins times six supported IDE versions times &amp;ldquo;does this still compile, does it still work, did they deprecate the API I depend on.&amp;rdquo; I did not plan for this when I built the first one.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-quarterly-update-cycle&#34;&gt;The quarterly update cycle&lt;/h2&gt;&lt;p&gt;Every JetBrains platform release can break plugin APIs. Sometimes it is a renamed method. Sometimes it is a removed extension point. Sometimes it is a subtle behavior change in the PSI tree that makes your completion engine return wrong results.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
