Skip to content

Fix verifyPlugin task - #296

Merged
devkanro merged 1 commit into
devkanro:mainfrom
anton-shchyrov:Fix-verifyPlugin-task
Aug 29, 2026
Merged

devkanro merged 1 commit into
devkanro:mainfrom
anton-shchyrov:Fix-verifyPlugin-task

Conversation

@anton-shchyrov

@anton-shchyrov anton-shchyrov commented Aug 26, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Title: Fix verifyPlugin task failing on plugin description validation

Description:

The verifyPlugin Gradle task was failing with:

Invalid plugin descriptor 'description'. The plugin description must start with Latin characters and have at least 40 characters.

Despite the message, the actual cause was the ✨ emoji in the ## ✨ What It Does heading inside the <!-- Plugin description --> block in README.md. IntelliJ Plugin Verifier validates the description's plain text against the regex ^[\w\s\p{Punct}\u2013\u2014]{40,} (ASCII word/whitespace/punctuation characters plus en/em dashes) for its first 40+ characters — any emoji in that range breaks the match, even though the error text suggests a "must start with Latin characters" issue.

Changes:

  • Removed the ✨ emoji from the ## What It Does heading in the plugin description section of README.md.
  • Bumped the foojay-resolver-convention plugin version from 0.8.0 to 1.0.0 in settings.gradle.kts.

Test plan:

  • ./gradlew clean verifyPlugin completes with BUILD SUCCESSFUL

@anton-shchyrov

Copy link
Copy Markdown
Collaborator Author

@Celend review, please

@Celend

Celend commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

@Celend review, please

Sorry I'm just contributor and can't merge, you may wait for @devkanro to review.

@devkanro
devkanro merged commit ef74fad into devkanro:main Aug 29, 2026
@devkanro

Copy link
Copy Markdown
Owner

@Celend

I don't have much bandwidth to maintain this plugin right now, so I've added you to the list of Contributors. If you're interested, you'd be very welcome to help me continue maintaining it.

Thanks

@anton-shchyrov

Copy link
Copy Markdown
Collaborator Author

@Celend Maybe you can launch a release action to push the current version of the plugin?

@anton-shchyrov
anton-shchyrov deleted the Fix-verifyPlugin-task branch August 29, 2026 10:42
@devkanro

Copy link
Copy Markdown
Owner

@anton-shchyrov I have also add you as a contributor, feel free to create release in future.

@anton-shchyrov

Copy link
Copy Markdown
Collaborator Author

@devkanro Thank you. But I still need your help. Publish plugin failed with message

Failed to upload plugin: Upload failed: You have not accepted the Plugin Developer agreement.

You should accept the new license agreement on the JetBrains website.

  1. Log into https://plugins.jetbrains.com/ with the account that owns the PUBLISH_TOKEN
  2. Navigate to the plugin page for io.kanro.idea.plugin.protobuf
  3. Accept the Plugin Developer Agreement
  4. Re-run the release workflow (or create a new release)

@devkanro

Copy link
Copy Markdown
Owner

@anton-shchyrov you don't need publish plugin by yourself, just publish the release in github, and github action will publish plugin ( now it have a error, I am trying to fix it.

https://github.com/devkanro/intellij-protobuf-plugin/actions/runs/33322994275

@anton-shchyrov

Copy link
Copy Markdown
Collaborator Author

@devkanro I understand the release cycle. And I wrote how to fix the publisher action. You need to accept the new license agreement and the publisher action will work.

@Celend

Celend commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

@devkanro Sure! at least I would keep it compatible to the latest Jetbrains verion. This plugin is very helpful to me and thanks for you creation!

@devkanro

devkanro commented Sep 1, 2026 •

Copy link
Copy Markdown
Owner

@anton-shchyrov I have fix the license issue, and I think the v2.6.0 is published


Oh it still under review.

@anton-shchyrov

anton-shchyrov commented Sep 8, 2026 •

Copy link
Copy Markdown
Collaborator Author

@devkanro
The plugin still hasn't appeared in the JetBrains marketplace. Maybe it makes sense to launch the release action again?
Because restarting an existing action crashes with an error that the version already exists

@devkanro

devkanro commented Sep 9, 2026 •

Copy link
Copy Markdown
Owner

@anton-shchyrov

Currently, due to a conflict with the official plug-in, it cannot pass the plugin verifier check. I have been communicating with Jetbrains, but have not received a reply yet.

image

@devkanro

devkanro commented Sep 9, 2026

Copy link
Copy Markdown
Owner

I have also created a post in the community, and you can follow Jetbrains’ replies and updates.

How to disable bundled plugins during plugin verification?

@anton-shchyrov

anton-shchyrov commented Sep 11, 2026 •

Copy link
Copy Markdown
Collaborator Author

@devkanro
protobuf -> protocol_buffers
prototext -> protocol_buffers_text

@devkanro

Copy link
Copy Markdown
Owner

@anton-shchyrov @Celend
The 2.6.0 now available in IDEs.

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.

4 participants