chore(deps-dev): bump bpy-addon-build from 0.3.0 to 0.5.1

[dependabot]

Bumps bpy-addon-build from 0.3.0 to 0.5.1.

Release notes

Sourced from bpy-addon-build's releases.

BpyBuild 0.5.1

Fix issue caught after the 0.5 release where using extension_settings::build_legacy, where the legacy build still ran with the extension action.

Full Changelog (Descending Order)

[0.5.1] - 2024-10-11

Fix: Make built-in extension action exit early when building legacy

Signed-off-by: Mahid Sheikh [email protected]

Fix: Rebuild Api object when legacy building to avoid extension action

Signed-off-by: Mahid Sheikh [email protected]

Chore: Update CHANGELOG.txt

Signed-off-by: Mahid Sheikh [email protected]

BpyBuild 0.5

After several months of work, BpyBuild now supports Blender Extensions!

What's New

[!CAUTION] The minimum Python version has now increased from Python 3.8 to Python 3.9, as Python 3.8 is now end of life.

• Support for building extensions
  • Right now, this is opt-in, so the build_extension option needs to be set in the config

  build_extension: true

  • In BpyBuild 0.6, extension building will be the default
  • BpyBuild also has the ability to build legacy addons alongside extensions with extension_settings::build_legacy:

  extension_settings:
  	build_legacy: true

  Note that you may have to override the extension action to include patching for stuff like bl_info removal. Eventually this will be a automatic part of BpyBuild
  • is_extension has been added to the BabContext object, to make it easy for actions to tell if a project is being built as an extension or not
• First release of lib_bpybuild_ext, a BSD licensed implementation of the Blender Extension builder.
  • Due to Blender being GPL licensed, we can't include the upstream extension builder in BpyBuild, so we had to reimplement it from scratch
  • The reimplementation is based on the extension docs, so there are known parity issues.
  • If you encounter any parity issues, please make sure it's documented on the extension docs. If it isn't, update the docs to make sure it's mentioned. Unless it relates to security, we won't accept lib_bpybuild_ext contribuitons that implement undocumented features.
• depends_on has been added for actions. This allows defining that an action depends on other actions to run before it. For example, with the following config, using the depend_dev action will raise an error if dev either isn't passed as well or if it's passed after depend_dev

  build_actions:
  	dev: 
      	script: "dev.py"
      	ignore_filters: 
        		- "*.blend"

... (truncated)

Changelog

Sourced from bpy-addon-build's changelog.

[0.5.1] - 2024-10-11

Fix: Make built-in extension action exit early when building legacy

Signed-off-by: Mahid Sheikh [email protected]

Fix: Rebuild Api object when legacy building to avoid extension action

Signed-off-by: Mahid Sheikh [email protected]

Chore: Update CHANGELOG.txt

Signed-off-by: Mahid Sheikh [email protected]

[0.5] - 2024-10-05

Fix: Make depends_on check occur before module loading

Signed-off-by: Mahid Sheikh [email protected]

Fix: Change action loading to account for additional actions

Signed-off-by: Mahid Sheikh [email protected]

Fix: Make extensions only install in 4.2+

Signed-off-by: Mahid Sheikh [email protected]

Fix: Resolve verification type checks caused by Python 3.8

Signed-off-by: Mahid Sheikh [email protected]

Fix: Fix error with dataclass initialization

Signed-off-by: Mahid Sheikh [email protected]

Fix: Use language-agnostic method for copyright validation

Signed-off-by: Mahid Sheikh [email protected]

Docs: Add documentation on config options

Signed-off-by: Mahid Sheikh [email protected]

Feat: Add depends_on for actions

This allows defining actions that require previous actions to execute beforehand, like debug actions for specific build configurations.

Signed-off-by: Mahid Sheikh [email protected]

Feat: Add --build-extension-only flag

... (truncated)

Commits

• 9dadbe4 Merge pull request #21 from Moo-Ack-Productions/milestone-5-1
• 153f052 chore: Update CHANGELOG.txt
• e5df18d build: Update version
• 8795029 fix: Make built-in extension action exit early when building legacy
• 2cec8de fix: Rebuild Api object when legacy building to avoid extension action
• 637494f Merge pull request #20 from Moo-Ack-Productions/milestone-5-0
• 000ea81 chore: Update CHANGELOG.txt
• 41008fd fix: Make depends_on check occur before module loading
• fac687f tests: Add test for depends_on
• 0e4d881 feat: Add depends_on for actions
• Additional commits viewable 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)