Repository navigation
feat: distribute NodeForge as a self-hosted Blender Extension - #39
Merged
Merged
Conversation
- Add Blender Extension manifest and release workflow - Bundle Math and L-System libraries for automatic installation - Bootstrap packages through the existing package manager - Support independent package updates without version downgrades - Remove Python execution permissions for Packages, Local and Examples - Make maximum NodeForge version advisory instead of blocking - Support Python imports under Blender Extensions namespace - Improve package installation safety and error handling
- Add repository_url to package manifests - Validate repository URLs using HTTP(S) schemes - Preserve backward compatibility with existing manifests - Keep repository metadata independent of UI and package updates
- Automatically refresh Packages, Functions and Examples - Defer catalog updates until Blender registration completes - Isolate catalog refresh failures - Add Blender Extension installation and integration tests - Validate bundled libraries and package upgrades before release
- Remove GitHub Release asset clobbering - Reject duplicate release publication - Restrict publication to release tag events - Keep manual workflow runs for validation only - Add release immutability regression tests
- Split workflow into build, publish-release and deploy-pages jobs - Reuse verified build artifacts across publication stages - Allow independent GitHub Pages deployment retries - Preserve immutable GitHub Release assets - Add deployment workflow regression tests
- Set GH_REPO explicitly in publish-release job - Support GitHub CLI execution without checkout - Add regression tests for repository resolution
- Remove redundant Local registry payload representation - Consolidate registry loading and validation - Handle duplicate package IDs without exception message matching - Preserve staging cleanup and registry compatibility - Add regression tests for both simplified paths
- Remove redundant nested exception handling - Handle fsync failures at the state publication boundary - Preserve file descriptor cleanup - Maintain existing package transaction guarantees - Add regression tests for fsync success and failure
- Move Blender integration tests into a dedicated test-extension job - Pass the built Extension ZIP between jobs through artifacts - Cache Blender 5.2 in build and test jobs - Require successful integration tests before release publication - Preserve independent GitHub Pages deployment retries - Bump NodeForge version to 0.72.7
denikryt
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Distribute NodeForge as a Blender 5.2 Extension.
bl_ext.*extension imports and optional packagerepository_urlmetadata.Required configuration
Set these GitHub Actions repository variables to direct URLs of the approved library Release ZIPs:
NODEFORGE_MATH_RELEASE_URLNODEFORGE_LSYSTEM_RELEASE_URL