You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the bug fixes in the latest release. However, the plugin install page can't work anymore. I'm not sure what problem it is since the developer console only shows 404 not found.
I suspect that there are two possible reasons:
The release branch name should be master instead of main according to the Official Release Guides. It seems that the setting of community-plugin repo doesn't specify branch property, so it uses the default branch setting (master). However, Github may redirect the master branch to the main branch, so I'm not sure whether this is the root cause.
The release name inconsistency. As mentioned in the latest release, there is no release version 1.3.7 in the Github repo, but the community plugin page shows that the latest version of the plugin is 1.3.7.
The text was updated successfully, but these errors were encountered:
Oh, no, the branch name doesn't matter, actually -- I've been using main since the beginning of the project without trouble. What is wrong is that I didn't quite perform the release steps correctly because I was in a bit of a rush and the release steps for this particular project are a little weird compared to my others.
I've just a moment ago kicked-off a new build & am fairly sure that'll fix things up.
Thanks for the bug fixes in the latest release. However, the plugin install page can't work anymore. I'm not sure what problem it is since the developer console only shows 404 not found.
I suspect that there are two possible reasons:
branch
property, so it uses the default branch setting (master
). However, Github may redirect the master branch to the main branch, so I'm not sure whether this is the root cause.The text was updated successfully, but these errors were encountered: