Readme update

[eliotwrobson]

See title, updates readme links to new documentation.

Also, removed the publish trigger for pushes to the develop branch. Once this is merged, all that's needed should be a merge to master! @caleb531 once that's done, I can open the submission.

[coveralls]

coverage: 99.64%. remained the same
when pulling 81d1a23 on eliotwrobson:new_links
into deea457 on caleb531:develop.

[caleb531]

@eliotwrobson Yep, looks good to me! Although from a philosophical perspective, I'm trying to figure out how I feel about merging to main without actually publishing a release. Because that would mean that main is no longer reflecting the latest published release, but rather, something in-development.

Maybe since we won't have published the tag yet, it won't matter? I suppose we could publish v9.0.0, but I think I would prefer to launch the docs site with the v9 for promotional purposes.

What are your thoughts?

[eliotwrobson]

@caleb531 I think that merging and then doing a v9 release for promotional purposes is fine (or even an 8.2). The only thing to note is that we'll probably have to do a release once the review is done, but I don't really mind multiple releases.

If you want to bundle the site with a v9 release, I'd say go ahead! The release notes should be minimal. Either way, I'd like to get the review started today, and we need the new links in the readme merged to main before we can get that going. I'll also go ahead and merge this PR.

[caleb531]

@eliotwrobson Now that I think of it, do we even have any breaking changes to warrant a v9 release? Here are all the commits/merges on develop that have not yet been merged to main:

• Enforce max line length of 88ch in flake8
• Added show_diagram method for Push Down Automata (Added show_diagram method for Push Down Automata #177)
• Add missing dependencies to requirements.txt
• Use PEP 517-compliant build backend
• Upgrade package dependencies to latest
• Revert "Upgrade package dependencies to latest"
• Fix bug: Replace * with *? in QuantifierToken regex pattern (Fix bug: Replace * with *? in QuantifierToken regex pattern #181)
• Add acknowledgement for Christopher Hampson
• fix: Minify for partial DFAs (fix: Minify for partial DFAs #184)
• Create CODE_OF_CONDUCT.md (Create CODE_OF_CONDUCT.md #190)
• Move CONTRIBUTING.md and add badges (Move CONTRIBUTING.md and add badges #191)
• Documentation site rework (Documentation site rework #189)
• Adding back missing docs (Adding back missing docs #196)
• Add docs workflow (Add docs workflow #195)
• Add setuptools
• Readme update (Readme update #197)
• Update copyright notice of docs index page (Update copyright notice of docs index page #198)

I suppose the only changes of substance are the show_diagram method for PDAs and the regex quantifier fix, but besides that, it's all housekeeping.

I've created a draft v8.2.0 GitHub release for you to look at—if you approve, I can go ahead and publish a v8.2.0 release!

[eliotwrobson]

@caleb531 I had the same thought, I didn't think there were any breaking changes that really necessitated a v9 release. I think the notes look good and I approve! Once the release publishes, I'll cc you on the submission later today.

[caleb531]

@eliotwrobson Excellent! I just published v8.2.0, and it's live now!:

https://github.com/caleb531/automata/releases/tag/v8.2.0
https://pypi.org/project/automata-lib/