# Initial plugin release is not published

**URL:** <https://platform.jetbrains.com/t/initial-plugin-release-is-not-published/571>\
**Category:** JetBrains Marketplace\
**Created:** [February 18, 2025, 1:35pm UTC](https://platform.jetbrains.com/t/initial-plugin-release-is-not-published/571 "2025-02-18T13:35:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lavrenkov](https://avatars.discourse-cdn.com/v4/letter/l/3da27b/32.png) [@lavrenkov](https://platform.jetbrains.com/u/lavrenkov)\
**Post date:** [February 18, 2025, 1:35pm UTC](https://platform.jetbrains.com/t/initial-plugin-release-is-not-published/571/1 "2025-02-18T13:35:19Z")

</div>

Hello,

We’ve submitted a [plugin](https://plugins.jetbrains.com/plugin/25655-openbpm/) on Feb 5 and got a bunch of issues and warnings, but the plugin was not published. Did I get it right that issues listed in red font are obligatory to fix? Are yellow ones the warnings which should be fixed, but they are not showstoppers for the plugin publication?

---

<div class="post-metadata">

**Author:** ![natalia.melnikova](https://sea1.discourse-cdn.com/flex001/user_avatar/platform.jetbrains.com/natalia.melnikova/32/31_2.png) [@natalia.melnikova](https://platform.jetbrains.com/u/natalia.melnikova)\
**Post date:** [February 18, 2025, 2:14pm UTC](https://platform.jetbrains.com/t/initial-plugin-release-is-not-published/571/2 "2025-02-18T14:14:39Z")

</div>

Hello,

Yeah, you are right! To get published, you have to address the issues marked red (which usually involves binary incompatibility and/or problems with API usages).

 ![image](https://us1.discourse-cdn.com/flex001/uploads/jetbrains_platform/original/1X/a3ac5b6f6df39088e96be6b3d3ae9f4b6e725460.jpeg)