Not uploaded correctly

[ashokdudhat]

Hi, you haven't updated it correctly

Hi,

We know that SVN can be tricky at times, let me help you with that.

👉 Before making any changes, please make sure you have read and understood the SVN documentation at https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/.

In general terms, you will need to include the latest plugin files at trunk/ , the versions in tags/[version]/ and the assets for WordPress.org in assets/ .

For example, the general structure of the code for a plugin releasing version 3.3.1 could look like this:
⚠️ This is an example of the structure of the plugin files in SVN, please do not use it directly, adapt it to your case.
plugins.svn.wordpress.org/wp-event-manager/
|-- trunk/
|---- readme.txt
|---- wp-event-manager.php
|-- tags/
|---- 3.3.1/
|------ readme.txt
|------ wp-event-manager.php

Let's check your current SVN step by step.

Your main SVN folder

This is the main folder of your SVN, accessible at https://plugins.trac.wordpress.org/browser/wp-event-manager.

It should have three main directories that you will use for your releases: assets/ , tags/ and trunk/ .

You should not add files to this directory, but to the subfolders mentioned above.

Analysis result:
✅ The trunk/ folder exists.
✅ The tags/ folder exists.
✅ The assets/ folder exists.
❌ Unexpected files/directories found: .project, Desktop.ini
In the SVN base directory there should be no files other than the main folders (assets, branches (optional), tags and trunk).
❌ Unexpected files found at tags/ : .project, Desktop.ini
Here we expect you to include only your version folders.

Your /trunk folder

Here is where the most recent code of your plugin is.

This should contain your plugin files: the readme, the main PHP file, other folders, etc.

You should not add these files to a subdirectory within /trunk , but directly to /trunk .

Analysis result:
✅ Readme file found at trunk/readme.txt .
✅ The Readme file trunk/readme.txt is declaring the version 3.3.1 through the "Stable Tag" parameter.
✅ Main PHP file containing the headers found at trunk/wp-event-manager.php .
✅ The main PHP file trunk/wp-event-manager.php is declaring the version 3.3.1 through the "Version" parameter.

Your /tags/3.3.1/ folder

This folder is where the code for your version 3.3.1 release is.

As the version declared in trunk/ is 3.3.1 the system will look for the contents of /tags/3.3.1/ and create the release from there.

Note that if you create /tags/3.3.1/ after you declared the version 3.3.1 at trunk/ , that version won't be released.

Analysis result:
✅ The tags/3.3.1/ folder exists.
✅ Readme file found at tags/3.3.1/readme.txt .
✅ The Readme file tags/3.3.1/readme.txt is declaring the version 3.3.1 through the "Stable Tag" parameter.
✅ The declared version at tags/3.3.1/readme.txt matches the version declared in trunk/readme.txt : 3.3.1 === 3.3.1
✅ Main PHP file containing the headers found at tags/3.3.1/wp-event-manager.php .
✅ The main PHP file tags/3.3.1/wp-event-manager.php is declaring the version 3.3.1 through the "Version" parameter.
✅ The declared version at tags/3.3.1/wp-event-manager.php matches the version declared in trunk/wp-event-manager.php : 3.3.1 === 3.3.1
ℹ️ The trunk/readme.txt was modified after tags/3.3.1/readme.txt
Fri, 16 Jan 2026 13:15:08 +0000 > Thu, 08 Jan 2026 08:52:25 +0000.
If you tried to release a new version, the files of the new version should have existed in tags/3.3.1/ before (or at the same time as) the new version was declared in trunk/readme.txt .
If this was the case, you can fix it by releasing a new version (remember to bump the version), making sure you create the folder in tags with the new version before or at the same time as declaring that version in trunk/readme.txt

[ritakikani]

I am removed file as per suggestion