Repository navigation
bump: preserve 0.9.0 release history for publication - #212
Merged
Merged
Conversation
Added maintainers section and updated contributors list.
…heck results against them - cobuild: include the user's explicit requirements in the delegated instruction and prefer verifying by reading the project. - SKILL: compare the result with the request, and mention any requirement that could not be confirmed. - dashboards/insights: the dashboard tile title can carry a requested title when a saved insight cannot be renamed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Dataiku forgets a future once its result is read, so resuming a finished build could never recover binding_failed or recovery_required. - Add code_env_name to ensure_plugin_code_env to bind an existing unbound PLUGIN_MANAGED environment of the plugin; recovery hints now point to it. - Check a resumed future_id from its peeked state before reading it, so another operation's result is never consumed, and explain a forgotten one. - Report a binding changed during the build as binding_changed, and surface Dataiku's reason for binding and creation failures. - Report created=true for a resumed build; refuse an interpreter or other environment for an already-bound plugin. - Detect R plugins from code-env/R/desc.json, Dataiku's actual layout. - Fix import grouping and the direct-write count in capabilities.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…esc.json A rebuild keeps the interpreter and core-package set an environment was created with, so correcting those in desc.json and rebuilding fails the same way. Verified on DSS 15.0: an environment created with LEGACY_PANDAS023 kept it after the descriptor was changed to AUTO and the plugin updated with rebuild_code_env. Route those failures to recreation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Split ensure_plugin_code_env into one helper per path (resume, create, bind) so the handler reads as a dispatch instead of a nested function returning tuples from six places. Behavior is unchanged. Type update_plugin's source as the same Literal as install_plugin and drop the runtime check the schema now enforces. Name the build timeout default. Cut the plugin guide's code-env section to what an agent decides before calling; per-outcome next steps live in the response hints. Correct the deletion note: on DSS 15.0, deleting a plugin removed its managed envs. Drop install tests that re-tested helpers update_plugin already covers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The README names plugins among its domains and reference areas like every other capability; installation and code-env details live in the plugin guide. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t on Keep a hint only where the next call is specific: resuming with future_id, binding with code_env_name, retrying a failed bind. Drop hints that restate the status or defer to the UI, the detection fields, and the version-pinned SDK comment. The plugin guide owns the remaining rules and now covers binding_changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The HTTP guard exists because a local path reads the server's filesystem. It blocked store installs and updates too, which read nothing local; it now applies to source='local_path' only. ensure_plugin_code_env only creates and binds an environment, refusing rather than replacing an existing binding, so destructiveHint is false. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ensure_plugin_code_env now advertises the same PythonInterpreter values as create_code_env instead of accepting any string. Docstrings say that local installs also return a future_id and that _resolve_source holds the HTTP check, the build-matching rule is explained again, and the guide's "Update sources" section is renamed "Sources" since it covers installs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs(skills): include explicit requirements in Cobuild requests and check results against them
chore: Added Contributors file
chore: refresh runtime lock for 0.9.0 release
get_dataset_metrics returned DSS's stored metric values with no freshness check. The built-in records:COUNT_RECORDS probe does not compute on build by default, so after a rebuild the tool kept reporting the old row count. The tool now recomputes the requested metrics on the current data before reading them (refresh=true by default). When recompute is skipped or fails, including engine failures DSS reports inside the computation report, the response says refreshed=false, carries refresh_error, and lists stale_metric_ids whose values predate the last build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…192) * docs(skills): use R recipes and Shiny webapps only on explicit request Cobuild in DSS 15.1 cannot create or edit `r` recipes or `SHINY` (or `BOKEH`) webapps, but the skill routed both to Cobuild. Gate R behind an explicit user request, document the gap, and offer the closest Cobuild-supported alternative instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(tools): create and update R recipes and Shiny webapps directly Cobuild cannot create or edit r recipes or SHINY webapps, or start a Shiny backend (verified on DSS 15.0 and 15.1). Add create_r_recipe, update_r_recipe, create_shiny_webapp and update_shiny_webapp as the one fixed Cobuild-gap exception. They refuse every other type; deletion stays with Cobuild. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(tools): restart a Shiny backend without resending its code update_shiny_webapp with neither ui nor server now only restarts the backend. In agent trials, both Shiny agents resent their whole ui code just to restart after switching the project R environment. Skills: recipes.md no longer says container execution is the only direct recipe write, and the Shiny env guidance says dataiku is provided, after both agents' first env search for shiny + dataiku matched nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(tls): trust operating system certificate authorities * test(tls): isolate launcher SSL activation in unit tests * test(tls): allow server authentication in test certificate * docs(setup): diagnose HTTPS certificate verification failures * fix(instances): expose connection errors for setup diagnosis * fix(setup): show underlying connection test errors * fix(tls): upgrade truststore to 0.10.5 * fix(setup): improve connection errors and saved key display --------- Co-authored-by: pmasiphelps <pmasiphelps@gmail.com> Co-authored-by: Ned Martorell <32619850+nmartorell@users.noreply.github.com>
fix(datasets): recompute dataset metrics before reading them
…ugin-marketplaces
fix(plugins): align client identities and marketplace catalogs
* bump: finalize 0.9.0 * docs: correct 0.9.0 release notes after feature deferral --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: pmasiphelps <pmasiphelps@gmail.com>
nmartorell
approved these changes
Nov 5, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Restore the release branch history after #210 was accidentally squash-merged. The main and release/0.9.0 trees are identical; the resulting merge adds no file changes. GitHub’s comparison still shows the original release diff because its common ancestor predates the squash. A merge commit will record release/0.9.0 as its second parent, satisfying the existing publication checks without rewriting main or moving tags.
Approve this PR and let the release operator merge it with
gh pr merge --merge, or explicitly choose Create a merge commit. Do not squash or rebase. Publication must use this PR number, after CI passes on its exact main merge commit.