Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postmortem for 0.3.0 #66

Merged
merged 20 commits into from
Mar 20, 2023
Merged

Postmortem for 0.3.0 #66

merged 20 commits into from
Mar 20, 2023

Conversation

nrbgt
Copy link
Contributor

@nrbgt nrbgt commented Mar 16, 2023

References

Code changes

  • bump to 0.3.1
  • resolve yarn.lock
  • resolve .github/locks
  • update release.md
  • more badges tinkering (was missing env)
  • ensure more .github/**/*.md changes are picked up by prettier
  • ship "hot" wheel/sdist on RTD
    • e.g.
      • https://ipyforcegraph--66.org.readthedocs.build/en/66/_static/ipyforcegraph-0.3.1.tar.gz
      • https://ipyforcegraph--66.org.readthedocs.build/en/66/_static/ipyforcegraph-0.3.1-py3-none-any.whl
    • add to README.md
  • fix docs warnings
  • fail docs build on warnings
  • check for xref not wrapped in an a
  • remove __all__ from behaviors/_base.py so all the classes show up
  • dev
    • update ci/badges
    • release.md
    • pull_request_template.md
    • CONTRIBUTING.md
    • README.md
      • split ci/binder badges for main and dev
  • add nbqa

User-facing changes

  • n/a

Backwards-incompatible changes

  • n/a

@github-actions
Copy link

Try it on ⬅️ ReadTheDocs or Binder ➡️

@nrbgt nrbgt force-pushed the gh-65-postmortem-030 branch 2 times, most recently from ea0533e to 59c73a7 Compare March 16, 2023 18:17
@nrbgt nrbgt marked this pull request as ready for review March 16, 2023 18:49
.github/ISSUE_TEMPLATE/release.md Outdated Show resolved Hide resolved
@nrbgt nrbgt force-pushed the gh-65-postmortem-030 branch 2 times, most recently from 4e8724b to 3f01ecf Compare March 16, 2023 20:52
@nrbgt nrbgt changed the base branch from main to dev March 17, 2023 15:14
@nrbgt nrbgt requested a review from sanbales March 17, 2023 17:02
@nrbgt nrbgt mentioned this pull request Mar 17, 2023
18 tasks
Copy link
Contributor

@sanbales sanbales left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code changes look good, just some minor suggestions for the checklists

.github/ISSUE_TEMPLATE/release.md Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/release.md Outdated Show resolved Hide resolved
- [ ] 🐧`source envs/lock/bin/activate`
- [ ] 🪟 `call envs/lock/Scripts/activate.bat`)
- [ ] run `doit lock`
- [ ] commit the new locks
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should they re-run all the tests after re-locking? asking in case a new dependency breaks something, CI should catch that, and probably not necessary to explicitly call for it...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, naw: the idea is CI does the heavy lifting after you quickly set everything up. "Works on my machine," is a very real possibility after a resolve, CI gonna find it.

@nrbgt nrbgt merged commit c55d9e4 into jupyrdf:dev Mar 20, 2023
@nrbgt nrbgt deleted the gh-65-postmortem-030 branch March 20, 2023 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Release 0.3.0
2 participants