deps(actions): Bump actions/deploy-pages from 4 to 5#1
Closed
dependabot[bot] wants to merge 2 commits into
Closed
Conversation
…ugin authoring Mirrors the dryade-plugins-sdk/ subtree from DryadeAI/dryade-internal at phase 339 completion. Ships: - Plugin / Agent / Tool / Route / Config / HealthCheck / ManageableComponent Protocols (typing.Protocol + @runtime_checkable, zero core.* imports) - Supporting Protocols: KV, Leash, IsolationLevel, Auth, DB, Channels, Hooks, Logging - compute_plugin_hash_pair (CONTRACT_VERSION = 4, SHA-256 + SHA3-256, byte-identical to Dryade core's _compute_plugin_hash_pair) - ManifestV2 dataclass + bundled v2 JSON Schema (importlib.resources) - testing/ subpackage — FakeHost, MockKV, MockConfig, MockLLM, factories for hermetic plugin pytest without Dryade core - 177 tests (54 protocol + 44 security-disclosure + 31 brand-leak + 26 examples-build + 22 docs-links/examples) - 5 runnable example plugins (hello_world, with_tool, with_llm, with_ui, multi_agent) - mkdocs-material documentation site (deploys to sdk.dryade.ai) - 10 GitHub Actions workflows: CI matrix py3.11/3.12/3.13, OIDC PyPI publish on v* tag, docs, OpenSSF Scorecard, CodeQL, dependency-review, labeler, welcome, release-drafter, all-contributors - README v2 with hero, badges, Star History, demo embed - SECURITY.md (GitHub Security Advisories + security@dryade.ai) - CHANGELOG.md (Keep-a-Changelog) - CONTRIBUTING.md with server-enforced branch policy - CODE_OF_CONDUCT.md (Contributor Covenant 2.1 by reference) - LICENSE (DSUL — Dryade Source-Usable License) - Issue templates + PR template + label set + .all-contributorsrc - llms.txt manifest for AI crawler discovery License: LicenseRef-DSUL (PEP 639). Python 3.11+. Built with Hatchling. Hash contract: v4 (SHA-256 + SHA3-256). Branch policy: server-enforced PR-gated (mirrors DryadeAI/Dryade:main). Co-Authored-By: Dammerzone <dammerzone@users.noreply.github.com>
Bumps [actions/deploy-pages](https://github.com/actions/deploy-pages) from 4 to 5. - [Release notes](https://github.com/actions/deploy-pages/releases) - [Commits](actions/deploy-pages@v4...v5) --- updated-dependencies: - dependency-name: actions/deploy-pages dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to dryade-plugins-sdk! Thanks for your first PR.
Please confirm:
- Tests pass locally (
pytest -x) - Examples still build (
pytest tests/test_examples_build.py) - PR title follows Conventional Commits
A maintainer will review shortly. Want to be added to the All Contributors list? Drop a comment like @all-contributors please add @yourname for code.
DryadeCore
pushed a commit
that referenced
this pull request
May 20, 2026
… slot-range carry-over) Surfaced by the end-to-end sdk_proof plugin test. Four surgical fixes to the scaffold output + Jinja2 templates. NOT a release — gap #1 (host-side Plugin Protocol vs ABC mismatch, the real load-gate blocker) is a Dryade PR; v1.1.2 publish waits on that landing. Gap #2 — core_version_constraint upper bound rejects all 2.x cores 6 template files (starter/team/enterprise × dryade.json.j2 + plugin.py.j2) flipped from '>=1.0.0,<2.0.0' to '>=1.0.0'. Authors can tighten later if they need. Gap #3 — scaffold output didn't mention SIGHUP gunicorn after edits Added a 'For local Dryade dev iteration' block with the dryade-pm push + kill -HUP sequence the previous test proved necessary. Gap #5 — pip install -e .[dev] fails on PEP 668 system Python Added 'python -m venv .venv && source .venv/bin/activate' line BEFORE the pip install in the Next steps output. Quoted '.[dev]' so zsh globbing doesn't bite. Slot-range carry-over fix — the scaffold's tier-and-slots block still carried the fabricated 1-3/3-5/10+ slot ranges I corrected in the marketplace docs earlier but missed here. Replaced with the tier-reach framing matching dryade.ai/docs/plugin-development: starter/team/enterprise as breadth-of-reach decisions, with the real 5/15/25 end-user slot numbers cross-referenced to the pricing page.
DryadeCore
pushed a commit
that referenced
this pull request
May 26, 2026
…, #3, #5 + slot-range carry-over) Surfaced by end-to-end author testing. Four surgical fixes to the scaffold output + Jinja2 templates. NOT a release — gap #1 (host-side Plugin Protocol vs ABC mismatch, the real load-gate blocker) is a Dryade PR; v1.1.2 publish waits on that landing. Gap #2 — core_version_constraint upper bound rejects all 2.x cores 6 template files (starter/team/enterprise × dryade.json.j2 + plugin.py.j2) flipped from '>=1.0.0,<2.0.0' to '>=1.0.0'. Authors can tighten later if they need. Gap #3 — scaffold output didn't mention SIGHUP gunicorn after edits Added a 'For local Dryade dev iteration' block with the dryade-pm push + kill -HUP sequence the previous test proved necessary. Gap #5 — pip install -e .[dev] fails on PEP 668 system Python Added 'python -m venv .venv && source .venv/bin/activate' line BEFORE the pip install in the Next steps output. Quoted '.[dev]' so zsh globbing doesn't bite. Slot-range carry-over fix — the scaffold's tier-and-slots block still carried the fabricated 1-3/3-5/10+ slot ranges I corrected in the marketplace docs earlier but missed here. Replaced with the tier-reach framing matching dryade.ai/docs/plugin-development: starter/team/enterprise as breadth-of-reach decisions, with the real 5/15/25 end-user slot numbers cross-referenced to the pricing page.
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/github_actions/actions/deploy-pages-5
branch
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
1 participant
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.
Bumps actions/deploy-pages from 4 to 5.
Release notes
Sourced from actions/deploy-pages's releases.
... (truncated)
Commits
cd2ce8fMerge pull request #404 from salmanmkc/node24bbe2a95Update Node.js version to 24.x854d7aaMerge pull request #374 from actions/Jcambass-patch-1306bb81Add workflow file for publishing releases to immutable action packageb742728Merge pull request #360 from actions/dependabot/npm_and_yarn/npm_and_yarn-513...7273294Bump braces in the npm_and_yarn group across 1 directory963791fMerge pull request #361 from actions/dependabot-friendly51bb29dMake the rebuild dist workflow safer for Dependabot89f3d10Merge pull request #358 from actions/dependabot/npm_and_yarn/non-breaking-cha...bce7355Merge branch 'main' into dependabot/npm_and_yarn/non-breaking-changes-99c12deb21Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)