hotfix: -include-after-body in execution profiles

[validbeck]

Internal Notes for Reviewers

The latest version of Quarto breaks our existing notebook execution workflow, as it fixed a workaround dependency with the jupyter-widgets package:

FATAL (/opt/quarto/share/filters/main.lua:3977) An error occurred:
Error resolving include-after- unable to open file https://unpkg.com/@jupyter-widgets/html-manager@*/dist/embed-amd.js

Broken workflow run — Attached to this attempt to merge staging to prod last week: #712

Removing this explicit embed from the execution profiles solves the issue in my testing:

    include-after-body: 
      - https://unpkg.com/@jupyter-widgets/html-manager@*/dist/embed-amd.js

Fixed workflow run — This is attached to the draft PR #713 where these fixes were also applied.

[github-actions]

PR Summary

This pull request removes the inclusion of the Jupyter Widgets embed script (https://unpkg.com/@jupyter-widgets/html-manager@*/dist/embed-amd.js) from the include-after-body section in the Quarto configuration files for development, production, and staging environments. The removal of this script suggests that the functionality provided by Jupyter Widgets is no longer required or has been replaced by another solution. The freeze option in the execute section remains unchanged, maintaining its auto setting.

Test Suggestions

• Verify that the Quarto site builds successfully without the Jupyter Widgets embed script.
• Check if any functionality dependent on Jupyter Widgets is affected by the removal of the script.
• Ensure that the site renders correctly in development, production, and staging environments.
• Test the site for any JavaScript errors or missing functionality that might have been previously provided by the Jupyter Widgets script.

[nrichers]

LGTM! 🚀

Once think I noticed while reviewing is that Quarto is now at version 1.7, released April 28. We have had some breaking changes before — at a standup, let's discuss if we should consider pinning to a specific version of Quarto in GitHub to control how we upgrade better?

[validbeck]

And it works! cc: @nrichers

PR preview: https://github.com/validmind/documentation/actions/runs/14983202870/job/42091858283?pr=712
Staging: https://github.com/validmind/documentation/actions/runs/14983175565/job/42091773505
Prod: https://github.com/validmind/documentation/actions/runs/14983707903/job/42093452823