Repository navigation
develop to main sync for release v2.10.0 - #2382
Merged
Merged
Conversation
Merge pull request #2363 from rtCamp/develop
* Register GoDAM abilities for AI agents over MCP GoDAM registers 32 abilities with the WordPress Abilities API (WordPress 6.9+). With the MCP Adapter plugin installed, a GoDAM MCP server at /wp-json/godam/mcp lists each one as a tool, so AI clients can work with the library directly. - Media: list, inspect, find where an item is used, transcripts, library health. - Library: folders, moving media, editing details, importing from a URL. - Player: layers on videos (CTA, hotspot, form, poll, ad) and hotspots on images, chapters, per-video ad tag and thumbnail, and placing video, audio, image, document and gallery blocks on pages. - Settings: global ads and the out-of-view default. - Processing: transcription and retranscoding. - Analytics: video, layer, funnel, placement, revenue and top-product reads. Abilities reuse GoDAM's REST routes in-process, so each route's own permission and validation checks still apply, and every read of attachment data is bracketed by the attachment-lookup hooks like the rest of GoDAM. Read abilities are exposed by default; those that change data stay hidden until a site administrator ticks Settings › Writing › GoDAM and AI agents. Add-ons add their own ability namespace to the server through the rtgodam_mcp_ability_namespaces filter. * Guard the Abilities API calls so Plugin Check passes on WordPress 6.5 Plugin Check flags wp_register_ability() and wp_get_abilities() as needing WordPress 6.9 while GoDAM supports 6.5. Both are already unreachable on older WordPress, since Abilities bails before registering anything, but the check only accepts a function_exists() guard in the same file. * Report a CTA layer's full content when listing layers godam/list-layers and godam/add-layer now return a card CTA's description, image and layout alongside its heading, button and link, and an HTML CTA's markup. The description was saved but not reported, so an agent checking its own work concluded the text had been lost and rebuilt the card as HTML. * Fix the MCP abilities review items Security and access - where-is-media-used skips posts the user can't read, so private posts and other users' drafts are never named. - The GoDAM MCP server needs upload_files to open (transport permission callback). Before, any logged-in user could list the tools. - Retranscode one item: anyone who can edit that item (route and ability); Editors and above still retranscode anything. - New WP-CLI check (tests/wp-cli/mcp-api-key-check.php) runs every read ability with a stored test key and token and fails if either appears in any output or error. Bugs - Retranscode called the route with a trailing slash and always failed. - add-media-to-page no longer advertises a draft default, so an existing page keeps its status unless status is given. - import-media-from-url applies the multisite upload limit and quotas. - update-video-settings checks the thumbnail and ad tag before saving anything, so a failed call changes nothing. Free sites - Tools that need GoDAM Central say so in their description and return one error, rtgodam_plan_required, without a verified API key. MCP Adapter - destructive on writes that overwrite data, openWorldHint on tools that reach outside the site. - Input schemas get additionalProperties false, maxLength and maxItems. - The server is only created on MCP Adapter 0.7.0+ (WP_MCP_VERSION); otherwise it is skipped quietly. No Requires Plugins header. - Three MCP prompts: add a video to a page, organise the library, video performance report. Settings - Write tools are on by default; Settings > Writing stays the kill switch. - New MCP on/off switch (rtgodam_mcp_enabled): on for new installs, off for sites that update. Shown in GoDAM > Settings > General with the server address and links to Application Passwords and Settings > Writing. Also: @SInCE n.e.x.t, unit tests for the shared rules, POT regenerated. * Hide GoDAM from every MCP server when the MCP switch is off Tested on a site with the switch off: the MCP Adapter's default server still listed all GoDAM tools and prompts, because they were marked public for MCP. Now the switch sets meta.public and meta.mcp.public to false on every GoDAM ability, so no MCP server offers them. The WordPress Abilities REST API is unchanged. * Show the AI agents panel's links as links GoDAM's settings page styles plain anchors like body text, so the three links in the panel did not look clickable. Use WordPress link buttons. * Fix the MCP switch turning off, cap URL imports, and hide abilities from REST when MCP is off - Register the MCP switch in its own settings group. In the 'general' group, saving Settings > General set it to false, because that page's form has no field for it. - Remove rtgodam_mcp_enabled and rtgodam_expose_write_abilities when the plugin is deleted. - godam/import-media-from-url stops at the Media Library's upload size limit on every site, not only multisite, so an import cannot fill the disk. - With the MCP switch off, GoDAM abilities are also hidden from the WordPress Abilities REST API. - Mark godam/move-media-to-folder and godam/retranscode-media as destructive. * Turn the MCP switch on by default on every site It was on for new installs and off for sites that update. Nothing can connect until an administrator installs the MCP Adapter plugin and creates an Application Password, and that is the opt-in, so updated sites no longer need an extra step. This also removes the new-install detection, which counted a site never opened in wp-admin as new. * Add the AI agent notice, next steps in ability errors, and review fixes - Notice on GoDAM's pages for administrators when the MCP Adapter is active and the MCP switch is on: links to the AI agents settings and https://godam.io/docs/ai-agents/, dismissible per user, removed on uninstall. - Every ability error now ends with a next step: another ability to call, what to change, or where an administrator should go. REST permission refusals get a shared hint. - godam/import-media-from-url refuses before downloading when the site's upload limit is zero. - The MCP and write switches are stored as 1 or 0, so the settings REST route no longer reports an invalid stored value after turning one off. - godam/move-media-to-folder is not marked destructive: with idempotent it made the Abilities REST route accept DELETE only. * Answer the PHPCS warnings on dynamic capabilities, switch_to_blog and get_posts Each flagged call is correct as written; the ignore comments say why. * Take out the GoDAM Central media abilities committed by mistake godam/list-central-media and godam/add-central-media were unfinished work in the same checkout and are not reviewed. The previous commit picked them up; this removes them again. * Let agents list GoDAM Central media and add it to the site's library Adds godam/list-central-media (read) and godam/add-central-media (write), wrapping the two routes the Media Library's GoDAM tab uses. An agent can now start from an empty library and bring in media that already lives on GoDAM Central, which can then be transcribed. The agent gives only the item's ID. Its address, type and stream addresses are read from GoDAM Central with the site's key, so a caller cannot create a library entry pointing at an address of its choosing. Both need a GoDAM plan, are flagged open-world, and never return the API key. No existing ability or route changes. * Let add-media-to-page take the page by URL, path or exact title An agent often knows a page's address or title but not its ID, and GoDAM has no page listing (that belongs to WordPress). The new 'page' input is resolved inside the ability: a URL or path on this site, or an exact title that matches one page. Only pages the user can edit are found, so the lookup never confirms a page they cannot edit exists. post_id works as before. * Test the URL import size limit and how the switches are stored - godam/import-media-from-url: a file over the Media Library limit is refused and deleted, the download stops one byte past the limit, other requests are not limited, and nothing downloads when the site takes no uploads. - The MCP and write switches are stored as 1 or 0. * Let the update abilities run with POST on the Abilities REST route WordPress's run route wants DELETE for an ability that is both destructive and idempotent, so update-media-details, update-site-settings, update-video-settings and set-chapters refused POST with a 405. They are no longer marked idempotent. remove-layer stays DELETE, as a real removal. MCP calls were not affected. A new test registers every ability and checks that only godam/remove-layer is DELETE-only. * Tell agents to pass an existing page as 'page', not 'title' In a claude.ai test the agent passed the existing lesson pages' names as title and so created three new draft pages. The description now says title always creates a new page and page finds an existing one. * Add to an existing page when add-media-to-page gets its exact title In two claude.ai takes the agent passed existing lesson pages' names as title, despite the description, and created duplicate drafts. Now a title that matches exactly one page of that type the user can edit (published first, then drafts) adds to that page. Two or more matches, or none, still create a new page. Tried over MCP: an existing title reused page 9; a new title created a draft. * Answer the PHPCS get_posts warnings on the page and Central media lookups Each is a capped lookup run on request by a signed-in user; the ignore comments say why. * Fetch transcripts only from GoDAM's CDN or this site, cap number inputs, and read boolean inputs strictly - godam/get-transcript fetched whatever URL was stored as the transcript path and returned its body. It now fetches only from GoDAM's CDN or this site's own host, follows no redirects and stops at 2 MB. - A number input with no maximum accepted 1e999, which PHP reads as infinity. A layer saved with it could not be turned into JSON, so every read of that media failed. Every number input now gets a maximum. - The string "false" was read as true for the player settings, allow_skip and global ads. These go through rest_sanitize_boolean(). * Let add-media-to-page add media to LifterLMS courses and lessons The ability accepted only pages and posts, so an agent could not put a video on a lesson: a gap for course sites. With LifterLMS active, an existing course or lesson is now a valid target, by post_id or by page (URL, path or exact title). These types have no core REST route, so they are saved with wp_update_post after the same edit_post check; publishing needs the type's publish capability. New items are still only pages and posts. The list is filterable (rtgodam_ability_host_post_types). Tried on a local site with LifterLMS 11: video added to a lesson by ID and to a course by title. * Add media to WPBakery pages as GoDAM's WPBakery element godam/add-media-to-page appended a block-editor block to every page. On a page built with WPBakery that block sat outside the builder's rows and could not be edited in the WPBakery editor. On a WPBakery page (one with [vc_row] in its content, or with the WPBakery editor turned on) the media now goes in as GoDAM's own WPBakery element, godam_video, godam_audio, godam_image, godam_document or godam_video_gallery, in a new row at the end. Video player settings use the attribute names the element saves, so it opens with them in the WPBakery editor. Block-editor pages and new pages are unchanged. * Pin today in the DateRangePicker custom-range test The test labels 7 to 13 Nov 2026 as a custom range. On 13 Nov 2026 that range is exactly "Last 7 days", so the label became the preset's and the test failed. Today is now pinned to 15 Jan 2026 for this test. * Report a skipped retranscode as an error, not as queued The retranscode route answers 200 with skipped: true when it does not send the job: a local site, virtual media, migrated Vimeo, storage over the limit, HTTP auth, an unsupported document or a Central refusal. godam/retranscode-media only turned HTTP errors into errors, so for all of these it returned accepted: true and told the agent that transcoding runs in the background. A skipped answer is now returned as a WP_Error. The code is the route's reason (for example virtual_media or storage_exceeded), the message is the route's own text as plain text (the route builds it with esc_html), and the status is 409. A job the route sent is still reported as accepted. Addresses review: #2341 (comment) * Save the video thumbnail before the ad source in update-video-settings godam/update-video-settings checked its input first but then saved the ad source before it called GoDAM for the thumbnail. When the thumbnail route failed after the input checks passed, the call returned an error with the ad source already switched, although the code comment said a failed call changes nothing. The thumbnail step now runs first and the ad source, a local meta save, goes last, so a failed GoDAM call leaves the ad source as it was. The comment now says what is guaranteed: invalid input changes nothing, and the call that talks to GoDAM goes first. A failed meta save after a good thumbnail can still leave the thumbnail changed. Addresses review: #2341 (comment) * Allow a chapter to run one second past the stored media length godam/set-chapters compared every chapter start and end with the media's stored length and refused anything past it. That length is _video_duration, which WordPress stores rounded to a whole second, so a last chapter ending at 45.4 on a file stored as 45 was refused as ending after the end of the media, while the media editor accepts it because it compares with the player's own unrounded length. resolve_ranges() now refuses a start or end only when it is more than Chapter_Abilities::DURATION_TOLERANCE (one second) past the stored length, and the messages still quote the stored length. A file WordPress misreads as much longer is still not caught, because the stored figure is all the ability has; the ability already labels it local_metadata. Addresses review: #2341 (comment) * Carry a rounded-up second into the minute in the chapter clock text The clock-style copy of a chapter time (originalTime and originalEndTime) formatted the seconds with %05.2f without carrying. A start of 59.996 rounded up to 60.00 and was written as 00:60.00, 119.996 as 01:60.00 and 3599.999 as 59:60.00. The ability keeps three decimals, so such values do reach clock(). clock() now rounds to the two decimals it shows before splitting into hours, minutes and seconds, so those values read 01:00.00, 02:00.00 and 01:00:00.00. The stored startTime and endTime keep their exact values. Addresses review: #2341 (comment) * Take the import file's extension from the download when the URL has none godam/import-media-from-url named the file only from the URL path. A download link with no extension in its path (/get?id=42, /download/12345) gave the names get and 12345, and core's sideload refuses a file with no extension as a disallowed type, so the import failed after the whole file was downloaded. Core's download_url() already names the temp file from the response's Content-Disposition or Content-Type. When the path gives a name with no extension, the ability now appends the temp file's extension (and uses the name import when the path gave no name at all), so the sideload gets get.mp4. A temp file that is still .tmp, or has no extension, leaves the name as it was, and a response with neither header still fails with core's file-type error. Addresses review: #2341 (comment) * Regenerate the POT for the review fixes Only line references in four ability files moved; no strings changed. * Refuse a title that matches a published page in add-media-to-page A title names a new page, so it must not change a live page by accident. When the title matches a published page, the ability now returns rtgodam_title_matches_published_page, which names the page and says to pass it as page or post_id. A title that matches one draft, pending, private or scheduled page still adds to it, so agents do not make duplicates. Addresses review: #2341 (comment) * Find a GoDAM Central item by type and title, and retry a failed list request godam/add-central-media read the whole GoDAM Central list on every call, 100 items at a time, videos first. On an account with hundreds of items one add took 10 to 36 seconds, and one failed list request failed the add: a real claude.ai run got 9 failed calls while adding six images. The tool now takes the item's type and title from godam/list-central-media as optional inputs and searches for it in one request, falling back to the full read. Every list request is tried once more before the error is returned. The item's address still comes only from GoDAM Central. Measured on the rtCamp Test account: 25.4 s without the inputs, 1.7 to 3.4 s with them. * Write the WPBakery gallery as handpicked_items so the element shows its videos godam/add-media-to-page added a video gallery to a WPBakery page as [godam_video_gallery mode="handpicked" ids="3,4"], but the gallery element edits its videos as the handpicked_items param group and has no ids field. Opening the element showed Handpicked mode with no videos picked, and a change made there was ignored, because Godam_Video_Gallery::render() reads handpicked_items only when ids is empty. The gallery now goes in as handpicked_items, the rawurlencoded JSON of one video_id row per video, the way WPBakery saves it, and ids is not written. The element opens with the videos picked, and what the editor saves is what renders. Addresses review: #2341 (comment) * Never return the GoDAM API key or account token from any ability Every ability's execute callback, in GoDAM and in add-ons that use Ability_Group, is now wrapped last so its result is scrubbed before it reaches an agent: the stored API key and account token are replaced with [redacted] in strings, array keys and values, objects, and WP_Error messages and data. This covers text that a route or GoDAM Central passes through, not only what the abilities build themselves. Placeholder values such as 'unverified' are left alone. * Reuse a draft with the title even when a published page has the same title godam/add-media-to-page looked for a published match first, so a published page and a draft with the same title were refused with rtgodam_title_matches_published_page instead of adding to the draft. The descriptions promise that one unpublished match is reused, and passing the title as page did not help either: that lookup sees two matches and finds nothing. The draft could only be reached by an ID the agent did not have. existing_page_for_title() now looks for one editable draft, pending, private or scheduled page first and returns it. A published match is refused only when there is no single unpublished page to reuse, so two unpublished pages next to a published one are still refused, and two unpublished pages alone still create a new page as before. find_by_exact_title() takes the statuses to look in and makes one query. The docblocks and the two descriptions say the same. Addresses review: #2341 (comment) * Use the WPBakery shortcode path only when WPBakery is active and the page is its own is_wpbakery_page() did not check that WPBakery is active, and the editor flag alone was enough. On a site where WPBakery was deactivated, a page that still had [vc_row] got [vc_row][vc_column][godam_video ...] added, and the row wrappers showed as text. A page with the flag but block or plain content got the shortcode glued onto its last block, as <!-- /wp:paragraph -->[vc_row].... The check now needs WPBakery to be active (WPB_VC_VERSION is defined). With it active, a page is a WPBakery page when its content has [vc_row], or when the editor flag is on and the page is still empty, which has nothing to glue onto. Any other page gets the block with the usual blank line before it. Addresses review: #2341 (comment) * Prefix a skipped retranscode's error code and add a next step where the route names none godam/retranscode-media used the route's bare reason as the error code (virtual_media, local_environment, preflight_failed), while the fallback and the other ability errors are rtgodam_ codes. The code is now rtgodam_retranscode_ plus the reason, for example rtgodam_retranscode_virtual_media, and rtgodam_retranscode_skipped when the route gives none. Some route messages ended without a next step. A skipped retranscode on a local site, of an unsupported document, or refused by GoDAM Central (preflight_failed or job_refused) now has one appended: try again on a site that is online, use godam/list-media with type document to find a supported file, or fix what the message names and call the ability again. Messages that already end with a step (virtual_media, migrated_vimeo, storage_exceeded, http_auth_enabled) are unchanged. Addresses review: #2341 (comment) * Take the import file's extension from the download when the URL's is not a media type godam/import-media-from-url took the temp file's extension only when the URL path had none. A link such as stream.php?id=42 that serves an MP4 kept the name stream.php, and core's sideload refused it as a disallowed type after the whole file was downloaded. The ability now takes the temp file's extension whenever the extension in the URL path is not an allowed type, so stream.php?id=42 serving an MP4 is sideloaded as stream.mp4. The temp file's extension is adopted only when it is an allowed type itself, so a .tmp file, no extension, or a disallowed name from Content-Disposition (.php) still ends in core's file-type error. The name from the path stays as the stem, because the temp file's own stem has a random suffix. languages/godam.pot is regenerated here too, for the descriptions changed in the page-title commit and the next steps added in the retranscode commit. Addresses review: #2341 (comment) * Regenerate the POT after merging the branch head Only line references moved. * Keep the account token in ability results; redact only the API key The account token is the organisation's public CDN subdomain (<token>.gdcdn.us), so it is in every GoDAM video URL. Replacing it turned those URLs into [redacted].gdcdn.us. Only rtgodam-api-key and rtgodam-api-key-stored are redacted now. Verified on a local site with the org's real key: a temporary must-use plugin appended the key to every string returned by the godam/v1 and wp/v2/media routes the abilities call. Over real HTTP (Abilities REST run route and the /godam/mcp server, Application Password auth) the 17 read abilities returned 240 planted copies, all redacted, 0 leaks. With the wrapper turned off the same run leaked the key in 7 calls. * Stop the Central media lookup piling up retries when GoDAM Central is down A failed title search now ends the lookup instead of moving on to more searches and a full read, which would hit the same outage. A retry runs only for a server or connection fault: a 4xx such as 401 for a revoked API key comes back the same every time. Worst case drops from 10 sequential calls (about 50 s) to 2. Addresses review: #2341 (comment) --------- Co-authored-by: Subodh Rajpopat <subodh.rajpopat@rtcamp.com>
godam/get-media returned an administrator's private attachment to an Author (title, type, upload time, job id, original file URL), though WordPress refuses the same user with 403. where-is-media-used and add-media-to-page had the same gap, because get_attachment() only checked the post type. get_attachment() now applies the Media Library routes' read rule: read_post, or upload_files for an inherit attachment. A refused ID gets the same 404 as a missing one, so IDs cannot be probed. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ter active (#2381) * List GoDAM abilities on the Abilities REST API only with the MCP Adapter active * Register GoDAM's abilities and categories only while the MCP Adapter is active
- Version 2.10.0 in godam.php, readme.txt, README.md, package.json and package-lock.json. - v2.10.0 changelog: AI agents through MCP, the switches, the admin notice. The release date is a placeholder (November XX, 2026) until the day is set. - readme.txt keeps the last three releases, so v2.8.1 drops out. - @SInCE n.e.x.t becomes @SInCE 2.10.0. - POT regenerated.
KMchaudhary
previously approved these changes
Nov 17, 2026
🔍 WordPress Plugin Check Report
📊 Report
|
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
0 |
mismatched_plugin_name | Plugin name "GoDAM - Video Hosting for LMS & Online Courses" is different from the name declared in plugin header "GoDAM". |
📁 assets/build/pages/video-editor.min.js (1 warning)
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
2 |
react_removed_api | This file calls "ReactDOM.findDOMNode", which was removed in React 19 and stops working once WordPress upgrades React. Use a ref on the element instead. |
📁 assets/build/css/main.css (1 warning)
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
0 |
EnqueuedStylesScope | This style is being loaded in all contexts. |
📁 assets/src/libs/analytics.min.js (5 warnings)
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
0 |
EnqueuedScriptsScope | This script is being loaded in all frontend contexts. |
0 |
NonBlockingScripts.NoStrategy | This script on http://localhost:8880 (with handle analytics-library) is loaded in the footer. Consider a defer or async script loading strategy instead. |
0 |
NonBlockingScripts.NoStrategy | This script on http://localhost:8880/2026/11/17/hello-world/ (with handle analytics-library) is loaded in the footer. Consider a defer or async script loading strategy instead. |
0 |
NonBlockingScripts.NoStrategy | This script on http://localhost:8880/sample-page/ (with handle analytics-library) is loaded in the footer. Consider a defer or async script loading strategy instead. |
0 |
NonBlockingScripts.NoStrategy | This script on http://localhost:8880/demo-attachment-post/ (with handle analytics-library) is loaded in the footer. Consider a defer or async script loading strategy instead. |
📁 assets/build/js/main.min.js (5 warnings)
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
0 |
EnqueuedScriptsScope | This script is being loaded in all frontend contexts. |
0 |
NonBlockingScripts.NoStrategy | This script on http://localhost:8880 (with handle rtgodam-script) is loaded in the footer. Consider a defer or async script loading strategy instead. |
0 |
NonBlockingScripts.NoStrategy | This script on http://localhost:8880/2026/11/17/hello-world/ (with handle rtgodam-script) is loaded in the footer. Consider a defer or async script loading strategy instead. |
0 |
NonBlockingScripts.NoStrategy | This script on http://localhost:8880/sample-page/ (with handle rtgodam-script) is loaded in the footer. Consider a defer or async script loading strategy instead. |
0 |
NonBlockingScripts.NoStrategy | This script on http://localhost:8880/demo-attachment-post/ (with handle rtgodam-script) is loaded in the footer. Consider a defer or async script loading strategy instead. |
🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check
elifvish
reviewed
Nov 17, 2026
elifvish
left a comment
Collaborator
There was a problem hiding this comment.
Release checks for e93dfeb
Migrations
- ✅ No DB schema change and no patch. Nothing runs on update.
⚠️ New optionrtgodam_mcp_enabled: on for new installs, off for updated sites. Reversible by the admin switch.⚠️ New optionrtgodam_expose_write_abilities.uninstall.phpnow deletes both options.⚠️ Retranscode route permission changes. A user who can edit the item can now retranscode it. Not reversible without a rollback.- ✅ No composer or npm major bump. Abilities need WordPress 6.9+ and MCP Adapter 0.7.0+. Older sites skip them.
Consumers
⚠️ godam-for-woo2.5.0 (PR 276): it uses thertgodam_mcp_ability_namespacesfilter andAbility_Group. Release both together.- ✅ Other repos in the workspace: none affected. No match for the new hooks, route or option names.
Deploy checks
- Check that
godam.php,readme.txtandCHANGELOG.mdshow 2.10.0. - Open GoDAM > Settings > General. Check the AI agents panel. Check that MCP is off on an updated site.
- Turn MCP on with the MCP Adapter active. Check that
/wp-json/godam/mcpneeds a user withupload_files. - Turn MCP off. Check that no MCP server and no
wp-abilities/v1route lists a GoDAM ability. - Log in as an Author. Retranscode your own upload. Check that the call succeeds. Retranscode another user's upload and check for 403.
- Open the Media Library and a video page. Check that the transcoding status still shows.
- Watch
debug.logfor PHP fatal errors.
Rollback
- Install GoDAM 2.9.1 from the previous zip.
- Roll back GoDAM for Woo 2.5.0 first if it is active.
- Delete
rtgodam_mcp_enabledandrtgodam_expose_write_abilitiesif you want a clean state.
Local checks
- ⏭️ Not covered: PHPUnit and WP-CLI
mcp-api-key-check.php. The host has nophporcomposer. - ⏭️ Not covered: JS test
DateRangePicker/index.test.js. Not run, to keep this check short. - ⏭️ Not covered: QA of the dry-tag zip. QA owns it (godam-plugin-wp issue 106).
rudrakshi-gupta
approved these changes
Nov 17, 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 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.
What and why
Moves GoDAM 2.10.0 from
developtomainfor the release: abilities for AI agents over MCP. Release ticket: https://github.com/rtCamp/godam-plugin-wp/issues/106. Ships together with GoDAM for WooCommerce 2.5.0.Commits, all already reviewed and merged into
develop:Where to look
Nothing new: every commit was reviewed in its own PR. Check only that the list above is the whole diff and that
godam.php,readme.txtandCHANGELOG.mdsay 2.10.0.UI evidence
No new UI change here: each UI change was recorded in its own PR (#2341).
How to test
QA of the dry-tag zip from
mainagainst the checklist in https://github.com/rtCamp/godam-plugin-wp/issues/106.Risk
risk: mediumbecause it ships the whole MCP abilities feature; every part was reviewed and tested ondevelop.