Skip to content

Conversation

Nanaushi
Copy link

@Nanaushi Nanaushi commented Aug 5, 2025

I am submitting a new Community Plugin

Repo URL https://github.com/Nanaushi/community-plugin-localizer/releases/tag/1.0.0

Link to my plugin:

Release Checklist

  • I have tested the plugin on
    • Windows
    • macOS
    • Linux
    • Android (if applicable)
    • iOS (if applicable)
  • My GitHub release contains all required files (as individual files, not just in the source.zip / source.tar.gz)
    • main.js
    • manifest.json
    • styles.css (optional)
  • GitHub release name matches the exact version number specified in my manifest.json (Note: Use the exact version number, don't include a prefix v)
  • The id in my manifest.json matches the id in the community-plugins.json file.
  • My README.md describes the plugin's purpose and provides clear usage instructions.
  • I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugins's adherence to these policies.
  • I have read the tips in https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines and have self-reviewed my plugin to avoid these common pitfalls.
  • I have added a license in the LICENSE file.
  • My project respects and is compatible with the original license of any code from other plugins that I'm using.
    I have given proper attribution to these other projects in my README.md.

Copy link

github-actions bot commented Aug 5, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ The plugin ID is not valid. Only alphanumeric lowercase characters and dashes are allowed.
❌ Your latest release is missing the main.js file.
❌ Your latest release is missing the manifest.json file.


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

I changed the id name to all lowercase.
Copy link

github-actions bot commented Aug 5, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ Plugin ID mismatch, the ID in this PR (cplocalizer) is not the same as the one in your repo (CPLocalizer). If you just changed your plugin ID, remember to change it in the manifest.json in your repo and your latest GitHub release.
❌ Your latest release is missing the main.js file.
❌ Your latest release is missing the manifest.json file.


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

@Nanaushi Nanaushi closed this Aug 5, 2025
@Nanaushi Nanaushi reopened this Aug 5, 2025
@github-actions github-actions bot changed the title Add plugin:Community Plugin Localizer Add plugin: Community Plugin Localizer Aug 5, 2025
@ObsidianReviewBot ObsidianReviewBot removed their assignment Aug 6, 2025
@ObsidianReviewBot
Copy link
Collaborator

The automated review has not found any issues with your code, ready for manual review.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.

@Nanaushi Nanaushi closed this Aug 9, 2025
@Nanaushi Nanaushi reopened this Aug 9, 2025
Copy link

github-actions bot commented Aug 9, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ Unable to find a release with the tag 1.0.1. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

Copy link

github-actions bot commented Aug 9, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ Unable to find a release with the tag 1.0.1. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

@Nanaushi Nanaushi closed this Aug 9, 2025
@Nanaushi Nanaushi reopened this Aug 9, 2025
@Nanaushi Nanaushi closed this Aug 9, 2025
@Nanaushi Nanaushi reopened this Aug 9, 2025
Copy link

github-actions bot commented Aug 9, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ Unable to find a release with the tag 1.0.0. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.


This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.

@Nanaushi Nanaushi closed this Aug 9, 2025
@Nanaushi Nanaushi reopened this Aug 9, 2025
@Nanaushi Nanaushi closed this Aug 9, 2025
@Nanaushi Nanaushi reopened this Aug 9, 2025
@Nanaushi Nanaushi closed this Aug 10, 2025
@Nanaushi Nanaushi reopened this Aug 10, 2025
@Nanaushi Nanaushi closed this Aug 10, 2025
@Nanaushi Nanaushi reopened this Aug 10, 2025
@Nanaushi
Copy link
Author

To the Obsidian Team

I was just rereading the "submit your plugin" section, and I noticed that it says, "Please ignore the conflicts in this branch that must be resolved." I didn't ignore them, and instead fixed the conflicts as suggested by this bot. I apologize.

@ObsidianReviewBot ObsidianReviewBot removed their assignment Aug 10, 2025
@ObsidianReviewBot
Copy link
Collaborator

The automated review has not found any issues with your code, ready for manual review.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants