Release 1.0.0

[adamsilverstein]

Continues #34

• Merge: Make a non-fast-forward merge from your release branch to develop, then do the same for develop into master. master contains the stable development version.
• Push: Push your master branch to GitHub, e.g. git push origin master.
• Wait for build: Head to the Actions tab in the repo and wait for it to finish if it hasn't already. If it doesn't succeed, figure out why and start over.
• Check the build: Check out the stable branch and test for functionality locally.
• Git tag: Create the release as 1.0.0 on the stable branch in GitHub. It should now appear under releases and in the WordPress admin as an update as well.
• Edit the 1.0.0 milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close 1.0.0 milestone
• If any open issues or PRs which were milestoned for 1.0.0 do not make it into the release, update their milestone to 1.1.0 or Future Release

[jeffpaul]

Confirming a Slack conversation with @johnwatkins0 that we both feel we're ready for a v1 release. As this is our initial release, we'll do so here first on GitHub and then submit the ZIP to the Plugin Review team on .ORG and await their review before this officially hits the .ORG repo.

[johnwatkins0]

Ready to go, @jeffpaul . The only thing is the GH deploy action failed, which I assume is expected because the .org repo doesn't exist yet: https://github.com/10up/autoshare-for-twitter/commit/e61b2cac151e5fafc5b0a3cdab0fb3c679df865e/checks

[jeffpaul]

@johnwatkins0 we'll want to confirm the release ZIP file contains only the files needed to submit to .ORG, once you can confirm that we'll submit to the Plugin Review team and await their response.

[johnwatkins0]

@jeffpaul Just to make sure I understand the process here -- for this initial release to .ORG, we need a copy of the plugin that doesn't have the unneeded files and does have the built assets and production dependencies (as opposed to the the zip automatically attached to the GitHub release, which contains the source code from the released branch). Future releases can be handled by the plugin deploy action, but this first one is manual. Do I have this right?

[jeffpaul]

@johnwatkins0 completely correct, yep!

[johnwatkins0]

Hey, @jeffpaul . Here's a zip that contains what's needed and only what's needed for the plugin to run. Let me know if this does the trick.

autoshare-for-twitter.zip

[jeffpaul]

I added in the readme.txt and submitted to .ORG, we're currently 15th in line for review so I'm not expecting to hear back until mid-January. I'll go ahead and close the 1.0.0 milestone and we can start looking at enhancements for a next release to milestone (alongside anything the .ORG Plugin Review team asks for).