build(deps): bump beancount from 2.3.6 to 3.0.0

[dependabot]

Bumps beancount from 2.3.6 to 3.0.0.

Changelog

Sourced from beancount's changelog.

======================== beancount: CHANGES

Note: This file contains a list changes in the 'v2' branch. The master branch will rely on the Git repository history.

2024-06-16

• Created branch 'v3' and released 3.0.0

  Based on our recent discussion around Beancount branches being confusing, I did the following to branches:

  • v2: remains the same (no change); but v2 is now even less subject to freeze exceptions than before, because v3 is now officially born and PyPI releases will be made for it.  The default reply to patches to v2 will be "move that to v3."

  • cpp: I turned the previous master branch's state with all C++ and Bazel build into a new 'cpp' branch. All work on the C++ rewrite -- if it is to continue -- will live on that branch. If things do move to Rust, I will probably salvage bits and pieces of that manually into a 'rust' branch. In particular, the schema defined in the proto files is something I'd like to carry forward (nicely documented and distinguishes between the pre and post interpolation data structures explicitly), and perhaps the new reFlex parser will be useful at some point.

  • v3: a new branch, to contain the state of the master branch MINUS the C++ bits. As stated above, the C++ code remains only on branch 'cpp'. This is now the official release branch and PyPI releases will be made of it.

  • master: this branch is now where new work on v3 might live. I'm not sure we really need it or what it should mean, but it should track v3 for now.

  I've reviewed missing PyPI releases and made sure we have these:

  https://pypi.org/project/beancount/ https://pypi.org/project/beangulp/ https://pypi.org/project/beanquery/ https://pypi.org/project/beanprice/ https://pypi.org/project/beangrow/ https://pypi.org/project/beancount2ledger/

  ​The inclusion of v3 releases for PyPI and new PyPI releases for subprojects should normalize the versioning situation in Beancount. Note that packaging and following other people's conventions are not my forte (and I don't use PyPI for my own projects I just use source), if you have any suggestions or something's missing please reply to this thread. Thanks for your patience,

2022-02-15

• Released 2.3.5 with only a few minor bugfixes. Mainly released for 3.10.

2021-03-20

• Fixed #639: Released 2.3.4.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like beancount is up-to-date now, so this is no longer needed.