Changelog

3

3.2

3.2.0 (2026-08-02)

New Features
  • feat: start files and directories matched by a template repository’s .quartoignore unselected in the file picker shown by Use Template. They stay in the list and can be ticked back on; the ignore file states an intent, not a prohibition. When no picker is involved, they are excluded outright, matching quarto use template.
Bug Fixes
  • fix: record source and source-type without rewriting the rest of an extension’s _extension.yml. Installing, updating or using a template re-serialised the whole manifest from a fixed set of known keys, which dropped comments and any other top-level key the author had added, coerced version: 1.0 to '1', flipped quoting style, and reordered keys. The two fields are now patched line by line, so everything else stays byte for byte identical.
  • fix: stop Use Template from deleting a local template folder. The command removed whatever directory it had read the template from, and for a local source that directory is the user’s own folder rather than a temporary copy. Only the temporary directory extracted from a downloaded archive is removed now.
  • fix: copy template files from the template’s own folder when the repository is itself an extension, that is when _extension.yml sits at the top level rather than under _extensions/. The folder above the template was used instead, so Use Template pulled in that folder’s unrelated contents.
  • fix: remove the whole temporary directory extracted from an archive. The wrapper directory that a downloaded archive unpacks into was left behind in the system temporary folder after every template use.
  • fix: treat the workspace folder’s _extensions/ as the primary host. When the folder itself holds at least one installed extension, it is now the only install, update, template and brand target, and the only entry in the Extensions Installed view. Subfolders are no longer offered, so an extension development repository can no longer install into a copy such as docs/_extensions/. This already happened by accident for quartoWizard.autoProjectDetection set to true or subFolders; it now also holds for openEditors, and for workspaces that exclude _extensions through files.exclude or search.exclude.
  • fix: skip paths matched by the workspace folder’s .quartoignore when detecting Quarto project roots. Listing docs there keeps a documentation website out of the Extensions Installed view and out of the folder pickers.
  • fix: narrow what a source offers to install, using the same two rules that apply to the workspace. When a downloaded repository has extensions in its own _extensions/, copies found elsewhere in the archive, typically the vendored docs/_extensions/ of a documentation site, are no longer offered, and paths matched by the repository’s .quartoignore are dropped. Installing such a repository no longer opens a “This repository contains multiple extensions” picker when the repository ships a single extension. Neither rule can empty the list, so an archive that only ships extensions in ignored locations still installs.
API Changes

These affect consumers of the @quarto-wizard/core package only. Its version tracks the extension, so the removals below are breaking for library consumers despite the minor bump; neither removed symbol is used by quarto-extensions-updater.

  • refactor!: replace findAllExtensionRoots() with readArchiveExtensions(), which returns the discovered extensions together with the resolved repository root as an ArchiveExtensions object. Callers no longer derive the root by splitting the extension path on _extensions, which pointed outside the source for a repository that is itself an extension.
  • refactor!: remove writeManifest(). updateManifestSource() now patches the source and source-type lines in place instead of re-serialising the manifest, so a whole-file writer no longer has a caller.
  • feat: export readQuartoIgnore(), isQuartoIgnored(), quartoIgnoreGlobs(), and QUARTOIGNORE_FILENAME from filesystem, alongside the toRelativePosixPath() and isInside() path helpers.
  • feat: add temporaryDir to InstallResult. It is set only when the extraction directory is a temporary one the call created, so a local directory source, which belongs to the user, is never mistaken for something safe to delete.
Internal
  • test: build the link-rejection tar fixtures byte by byte instead of archiving a real link with node-tar, whose writer emits a late unhandled stream error when it walks a hard link. That error failed the suite intermittently (6 of 15 local runs, and the macOS CI job). The fixtures no longer skip themselves on platforms without link support.
  • build: extend the Prettier globs to packages/*/tests, which the formatter skipped entirely.
  • docs: generate the Project Detection, Update Behaviour and Linting sections of the configuration reference instead of hand-editing the generated page, and drop the Logging group, which matched no setting. configGroups entries in scripts/docs-config.json accept an optional notes block, and setting defaults are serialised with JSON.stringify, which fixes the unquoted subFolders in the example configuration.
Dependency Updates
  • chore(deps): upgrade @vscode/test-electron from 3.0.0 to 3.1.0. VS Code 1.131 dropped the Contents/MacOS/Electron alias from its macOS bundle, which made the test suite fail with spawn .../Contents/MacOS/Electron ENOENT.
  • chore(deps): add minimatch to @quarto-wizard/core for .quartoignore pattern matching. It was already present in the tree as a dependency of glob.

3.1

3.1.3 (2026-07-24)

Dependency Updates
  • chore(deps): upgrade npm dependencies to latest, including js-yaml 4.x to 5.x (YAML 1.2 core schema for parsing) and archiver 7.x to 8.x (class API in tests). tar is unpinned from 7.5.15 to ^7.5.21, picking up upstream security fixes; the previously worked-around abort regression no longer reproduces. Overrides force patched diff and serialize-javascript under mocha, bringing npm audit to zero findings. TypeScript stays on 6.x until typescript-eslint and typedoc support 7.x; @types/vscode stays aligned with the ^1.96.0 engine.
Bug Fixes
  • fix: stop installing the extension when the confirmation dialog opened by a vscode://mcanouil.quarto-wizard/install or /use link is dismissed. Cancelling the dialog, or pressing Esc, now aborts the operation as intended. The dialog no longer shows a redundant “No” button alongside the built-in Cancel, and it now states the destination folder so the target of the install is visible before confirming.

3.1.2 (2026-06-16)

Bug Fixes
  • fix: stop reporting valid attributes such as width on .column as Unknown attribute by default. The schema-unknown-attribute diagnostic is now opt-in via the new quartoWizard.lint.unknownAttributes setting (default false), since Quarto Wizard has no built-in schema for Quarto/Pandoc internals (#356).

3.1.1 (2026-06-14)

Bug Fixes
  • fix: do not flag spaces around = inside math such as \text{X = Y} as needing whitespace removal. Braces in LaTeX math are no longer treated as Pandoc attribute blocks, so inline attribute diagnostics only run in genuine attribute contexts (spans, links/images, code, divs, headers).

3.1.0 (2026-05-17)

New Features
  • feat: support a v2 extension schema vocabulary at https://m.canouil.dev/quarto-wizard/assets/schema/v2/extension-schema.json. v2 uses JSON Schema canonical names exclusively (minimum, maximum, multipleOf, additionalProperties, propertyNames, dependentRequired, contentEncoding, contentMediaType, replaceWith, …), drops pattern-exact in favour of ^...$ anchors in the pattern itself, and lets shortcode entries declare a parent-level required: [name1, ...] array. v1 schemas keep working under the v1 URI; the runtime dispatches on the instance $schema URI.
  • feat: extend the v1 schema vocabulary with new optional field properties: title, examples, format, null type, multiple-of, additional-properties, property-names, dependent-required, content-encoding, content-media-type. completion.type: directory is now recognised alongside file / color / … .
  • feat: $schema: completion in _schema.yml offers both the v1 and v2 URIs (v2 preferred).
  • feat: extend schema completion, diagnostics, and hover to YAML files included via metadata-files:. Secondary configuration files declared in _quarto.yml, _metadata.yml, or .qmd front-matter now receive the same IntelliSense as canonical Quarto config files.
Bug Fixes
  • fix: discover extension schemas across nested Quarto projects. YAML completion, hover, diagnostics, shortcode completion, element attribute completion, and snippet completion now resolve schemas through each document’s nearest enclosing project root instead of only the workspace folder, so extensions installed in sub-projects (for example repo/subProj/_extensions/...) populate IntelliSense for documents inside that sub-project.
  • fix: report an unknown-schema-version warning when a _schema.yml declares a $schema URI that is not one of the supported versions, and an invalid-schema-uri-type error when $schema is set to a non-string value, instead of silently validating against v1.
  • fix: flag stray name: on a field descriptor outside a shortcode argument (previously silently accepted); flag unknown keys on classes.* entries; report the camelCase keyPath in invalid-property-names when the author used propertyNames rather than property-names; warn when a single descriptor sets both the camelCase and kebab-case form of the same keyword (v1 only); reject type: content outside shortcode arguments; require shortcode positional arguments to declare a name.

3.0

3.0.1 (2026-05-12)

Bug Fixes
  • fix: do not flag {key="value"} inside inline code spans as needing whitespace removal. Backtick-wrapped attribute syntax in prose (for example, when documenting Pandoc attribute rules) is now correctly recognised as code and skipped by the inline attribute diagnostics.
  • fix: do not extract {...} patterns from YAML front matter as Pandoc attribute blocks. Curly braces inside literal block scalars (for example, Typst code under include-before-body) no longer trigger false-positive inline attribute diagnostics.

3.0.0 (2026-04-29)

New Features
  • feat!: narrow the default scope of quartoWizard.autoProjectDetection. The default is now "subFolders", which scans only direct children of the workspace folder. Set the value to true for the previous recursive behaviour.
  • feat!: quartoWizard.autoProjectDetection: true now means “recursive subfolder scan only”. It no longer also walks up from open files; set the value to "openEditors" for that behaviour.
  • feat: render auto-detected project roots hierarchically in the Extensions Installed view. Sibling sub-projects under a shared parent (for example docs/A and docs/B) are grouped under that parent; projects without shared parents stay flat.
Bug Fixes
  • fix: log a warning and fall back to "subFolders" when quartoWizard.autoProjectDetection is set to an unknown value, instead of silently using the workspace-folder fallback.

2

2.5

2.5.0 (2026-04-23)

New Features
  • feat: auto-detect Quarto project roots in workspace subfolders via the new quartoWizard.autoProjectDetection setting, modelled on VSCode’s git.autoRepositoryDetection. A folder qualifies when it contains _quarto.yml/_quarto.yaml or an _extensions/ directory with at least one installed extension. Detected roots populate the Extensions Installed view and every folder-targeted command (Install, Use Template, Use Brand, …). The setting accepts true (default), false, "subFolders", and "openEditors" with the same semantics as the Git extension.

2.4

2.4.1 (2026-04-19)

  • chore: no user-facing changes.

2.4.0 (2026-04-19)

Fixes
  • fix: update checks now respect each extension’s recorded source-type instead of always querying the Quarto registry. Registry-sourced extensions resolve against the registry; GitHub-sourced extensions resolve against GitHub releases and tags directly, with prerelease tags (e.g. v2.0.0-beta.1) skipped. By default there is no fallback between sources; set quartoWizard.update.crossSource to true to let GitHub-sourced extensions fall back to the registry when GitHub returns no release or tag.

2.3

2.3.1 (2026-04-15)

Dependency Updates
  • chore(deps): upgrade npm dependencies to latest, including undici 7.x to 8.x.
Fixes
  • fix: allow backticks inside quoted values in fence info strings, preventing false “Remove spaces around =” diagnostics.

2.3.0 (2026-04-13)

New Features
  • feat: add Quarto Wizard: Sign In with GitHub Session command to authorise Quarto Wizard to use your VSCode GitHub session for installing from private repositories.
  • feat: installing an extension or template from GitHub that returns a “not found” error now offers a sign-in prompt, covering private repositories that GitHub reports as 404 to unauthenticated requests.
  • feat: detect GitHub SAML SSO enforcement on 403 responses and offer an “Authorise” action that opens the organisation’s authorisation URL so the token can be granted SSO access.
Fixes
  • fix: signing in via the 401/403 authentication dialog now also persists the session opt-in flag so subsequent installs silently reuse the VSCode GitHub session without re-prompting.
Breaking Changes
  • breaking: rename Quarto Wizard: Clear GitHub Token (Manual)Quarto Wizard: Clear GitHub Authentication. The new command clears both the manually set token and the VSCode session opt-in. Command id changes from quartoWizard.clearGitHubToken to quartoWizard.clearGitHubAuth, so any keybindings bound to the old id must be updated.

2.2

2.2.2 (2026-03-23)

Fixes
  • fix: guard against false linting diagnostics with indented fenced code blocks.

2.2.1 (2026-03-12)

Fixes
  • fix: guard against false linting diagnostics inside code blocks with CRLF line endings (#301).

2.2.0 (2026-02-25)

New Features
  • feat: add schema-aware authoring support for extensions, including smarter completions and validation for YAML, shortcodes, and inline attributes.
  • feat: add extension-provided snippets with richer descriptions and previews.
  • feat: add compatibility details in the extensions tree, including required Quarto versions and compatibility status.
  • feat: improve extension source workflows and actions, including support for quarto use brand.
Fixes
  • fix: improve extension update reliability for commit-based sources and reduce refresh race conditions.
  • fix: resolve hangs during stream/drain operations to keep extension actions responsive.
  • fix: improve completion behaviour while typing, including better suggestion handling and fewer duplicate entries.
  • fix: harden security checks and provider robustness in extension workflows.
Documentation
  • docs: expand documentation for schema, snippets, and brand workflows.

2.1

2.1.3 (2026-02-05)

  • docs: update website theme and display proper license.

2.1.2 (2026-02-05)

Dependency Updates
  • chore(deps-dev): bump prettier from 3.7.4 to 3.8.1 (#244)
  • chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates (#246)
  • chore(deps): bump undici from 7.18.2 to 7.19.2 (#243)
  • chore(deps): bump lodash from 4.17.21 to 4.17.23 in the npm_and_yarn group across 1 directory (#241)

2.1.1 (2026-01-23)

Dependency Updates
  • chore(deps): bump tar from 7.5.3 to 7.5.4 in the npm_and_yarn group across 1 directory (#239)

2.1.0 (2026-01-20)

New Features
  • feat: add Quarto Wizard: Install Extension from GitHub command for direct GitHub installation with version specifiers (e.g., owner/repo@v2 or owner/repo@branch).
Refactoring
  • refactor: replace auto-detection with explicit source picker in “Install Extension” and “Use Template” commands. Users now choose the installation source (Registry, GitHub, URL, or Local) as the first step, enabling direct GitHub installation with version specifiers (e.g., owner/repo@v2 or owner/repo@branch) even for extensions in the registry.

2.0

2.0.1 (2026-01-19)

Dependency Updates
  • chore(deps): bump tar from 7.5.2 to 7.5.3 in the npm_and_yarn group across 1 directory (#234)
  • chore(deps): bump undici from 7.16.0 to 7.18.2 in the npm_and_yarn group across 1 directory (#233)

2.0.0 (2026-01-09)

Breaking Changes
  • removed: quartoWizard.quarto.path setting is no longer available.
  • removed: Quarto CLI is no longer required; extension management is now handled natively.
New Features
Core
  • feat: add @quarto-wizard/core package with platform-agnostic extension management logic.
  • feat: add proxy support via environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY).
Templates
  • feat: add interactive file selection for templates with tree view, allowing users to select which files to copy.
  • feat: add target subdirectory option for template files when using Quarto Wizard: Use Template functionality. Users can now specify a subdirectory within the project where template files should be copied, while extensions always install to the project root.
Extensions
  • feat: add multi-extension selection when installing from sources containing multiple extensions.
  • feat: add extension type filtering in the picker UI for easier browsing.
  • feat: add Quarto version requirement validation using the quarto.quarto extension API.
  • feat: support discovery and removal of extensions without owner in path (e.g., _extensions/myext).
Commands
  • feat: add Quarto Wizard: Install Extension from Registry command for direct registry installation.
  • feat: add Quarto Wizard: Install Extension from URL command for archive URL installation.
  • feat: add Quarto Wizard: Install Extension from Local command for local path installation.
  • feat: add Quarto Wizard: Update All Extensions command to batch update outdated extensions.
  • feat: add Quarto Wizard: Remove Multiple Extensions command for batch removal.
  • feat: add Quarto Wizard: Clear Extension Cache command to force registry refresh.
  • feat: add Quarto Wizard: Set GitHub Token (Manual) command for explicit token configuration.
  • feat: add Quarto Wizard: Clear GitHub Token command to remove stored token.
  • feat: add command descriptions to all commands for improved discoverability.
Settings
  • feat: add quartoWizard.cache.ttlMinutes setting to configure cache duration.
  • feat: add quartoWizard.registry.url setting to configure custom registry URL.
Documentation
  • docs: add Quarto-based documentation website with user guide and API reference.
  • docs: add API reference documentation generated from TypeDoc.
  • docs: add reference pages for commands, configuration, and environment variables.
Refactoring
  • refactor: replace Quarto CLI calls with native archive extraction and GitHub API integration.
  • refactor: migrate extension lifecycle operations (install, update, remove) to @quarto-wizard/core.
  • refactor: add single-pass installation with callbacks for overwrite confirmation and version validation.
  • refactor: improve authentication priority (manual token > VSCode session > environment variables).
  • refactor: centralise error handling with typed error classes.
  • refactor: use InstalledExtension type from core library instead of custom ExtensionData interface.
  • refactor: consolidate tree provider caching into single structured cache object.
  • refactor: extract reusable path resolution and source type detection utilities.
  • refactor: remove sync/async function duplication in extensions utilities.

1

1.0

1.0.2 (2025-12-06)

  • fix: ensure Quarto path validation properly awaits version check, add clear error messages with actionable buttons when Quarto CLI is not found, and implement detailed diagnostic logging for troubleshooting configuration issues.

1.0.1 (2025-10-27)

  • fix: update is using “version” instead of tag.

1.0.0 (2025-10-20)

Stable Release - This project has reached stable status!

  • No breaking changes from previous version.
  • All existing functionality remains unchanged.

0

0.20

0.20.1 (2025-10-19)

  • fix: prevent overwriting existing “source:” field in _extension.yml file (as it will come from quarto add command in the future).

0.20.0 (2025-10-14)

  • feat: add “Reveal in Explorer” command for installed extensions.
  • chore: polish code, comments, and documentation.

0.19

0.19.1 (2025-10-04)

  • docs: add walkthroughs for Quarto Wizard features.

0.19.0 (2025-09-29)

  • feat: add progress notification when updating or removing an extension from the Quarto Wizard Explorer view.
  • feat: implement timeout handling for network and Quarto version checks.
  • fix: drop markdownlint related code and settings.
  • fix: enable extensions caching with 30-minute TTL for improved performance and reduced network requests.
  • fix: migrate from child_process.exec() to child_process.spawn() for enhanced security and elimination of command injection risks.
  • fix: optimise tree view refresh operations to eliminate duplicate calls and ensure automatic updates after all actions.
  • fix: resolve promise properly when workspace folder is empty in installQuartoExtension() function.
  • refactor: Convert remaining forEach to functional array methods.
  • chore: polish code, comments, and documentation.
  • chore: update dependencies to latest versions.
  • chore: optimise README.md images.
  • chore: remove outdated test verification script.

0.18

0.18.6 (2025-05-02)

  • fix: ensure update check occurs after installing, updating, or removing an extension.

0.18.5 (2025-04-25)

  • feat: use error code from Quarto CLI >= 1.7.23 when installing an extension.

0.18.4 (2025-04-17)

  • fix: handle undefined source in repository field for extension tree

0.18.3 (2025-04-12)

  • chore: no user-facing changes.

0.18.2 (2025-04-12)

  • fix: proper handling of extension source with default tag

0.18.1 (2025-04-03)

  • fix: strip tag from source URL in /use?repo=<repository> handler.

0.18.0 (2025-04-03)

  • feat: add /use?repo=<repository> URI handler for installing Quarto extensions templates from the browser.
  • feat: enhance URI handling for Quarto extensions.
  • feat: enhance Quarto extension installation and template handling.
  • feat: documentation for Quarto commands.
  • feat: support extension tags in default Quarto installation.

0.17

0.17.0 (2025-03-31)

  • feat: support installing/using Quarto extensions templates.
  • fix: correct typo in short title of the quartoWizard.installExtension command.

0.16

0.16.2 (2025-03-22)

0.16.1 (2025-03-17)

  • fix: GitHub icon / “open source” visibility for tree elements without source.

0.16.0 (2025-03-15)

0.15

0.15.2 (2025-03-12)

  • feat: add a welcome view in the Quarto Wizard Explorer.
  • feat: handle empty workspace(s) in the explorer view.
  • feat: add workspace folder install context command.
  • fix: disable “blanks-around-fenced-divs” rule by default.
  • refactor(src/utils/workspace.ts): use vscode.WorkspaceFolderPickOptions() for workspace folder selection.
  • docs: add a note about the “blanks-around-fenced-divs” rule in the README.

0.15.1 (2025-03-10)

  • fix: tweak markdownlint extension activation and trigger to avoid linting issues.

0.15.0 (2025-03-09)

  • feat: add support for multi-root workspaces (#102).
  • feat: implement workspace folder selection utility (#100, #101).

0.14

0.14.2 (2025-03-06)

  • feat: add custom “markdownlint” rules: “blanks-around-fenced-divs”.
  • fix: set “markdownlint” linting to “on type” by default.
  • chore: remove a console.log() statement.

0.14.1 (2025-02-23)

  • feat: improve the SVG icon.

0.14.0 (2025-02-22)

  • feat: add URI handler for installing Quarto extensions from the browser.
    vscode://mcanouil.quarto-wizard/install?repo=mcanouil/quarto-iconify

0.13

0.13.0 (2025-02-22)

  • feat: allow to disable the automatic markdown linting via markdownlint with a “never” option.
  • refactor(lintOnEvent): use switch instead of if.
  • refactor: Use truthy checks instead for better readability..

0.12

0.12.0 (2025-02-21)

  • feat: automatic markdown linting via markdownlint.
  • feat: lazy extension dependencies.

0.11

0.11.0 (2025-02-20)

  • feat: first release of the Quarto Wizard extension, but not yet 1.0.0.

0.10

0.10.1 (2025-02-20)

  • chore: no user-facing changes.

0.10.0 (2025-02-20)

  • refactor: no longer use quarto remove to uninstall an extension.

0.9

0.9.0 (2025-02-20)

  • refactor: use a pre-fetched list of Quarto extensions for the QuickPick UI.
  • refactor: drop GitHub authentication requirement for the extension details.
  • refactor: change log level for cached extensions messages.
  • refactor: implement debounced logging for extension fetching via fetchExtensions()
  • feat: add activation log message for Quarto Wizard.

0.8

0.8.1 (2025-02-20)

  • fix: prevent error notification when extension details cannot be retrieved.

0.8.0 (2025-02-18)

  • feat: retrieve and display extensions details from GitHub API.
  • feat: add more details in QuickPick UI for extensions.
  • feat: set log to true for output channel, allowing colouring.
  • feat: add Quarto extensions update check.
  • fix: activate quarto-wizard-explorer view only in a workspace.
  • refactor: use constants variables for cache name and expiration time.
  • refactor: use logMessage function to log messages.
  • refactor: add a log level parameter to logMessage function.
  • docs: add GitHub account authentication as a requirement.
  • docs: update README.md with new features and usage instructions.
  • chore(CITATION.cff): add citation file.
  • chore: update TypeScript configuration settings.
  • chore: add basic Dev Container setup.
  • ci: bump version via GitHub Actions input.
  • docs: add JSDoc comments for utility functions and commands.

0.7

0.7.2 (2025-02-06)

  • fix(src/ui/extensionsQuickPick.ts): broken extensions install by updating description handling in QuickPick UI.
  • deps: update dependencies to latest.

0.7.1 (2025-02-02)

  • feat: add “activationEvents” to package.json to avoid unnecessary activation.
  • fix: GitHub button in QuickPick UI opens again the repository in the default browser.

0.7.0 (2025-01-30)

  • refactor(src/utils/network.ts): internal logging.
  • refactor(src/utils/extensions.ts): externalise Quick Pick UI tools.
  • refactor: use constants for log messages target.
  • fix(src/utils/extensions.ts): caching of the list of available Quarto extensions.
  • fix(src/utils/extensions.ts): update cache expiration time for extensions list and display in log as ISO string.
  • fix: harmonise log and notification messages.
  • chore: use webpack to bundle the extension.

0.6

0.6.0 (2025-01-24)

  • feat(package.json): add a “Quarto Wizard” menu in Explorer and Editor context menus.
  • fix(src/utils/reprex.ts): Quarto Wizard: Quarto Reproducible Document command no longer set filename.
  • fix(README.md): update commands and usage instructions.

0.5

0.5.5 (2025-01-21)

  • chore: no changes.

0.5.4 (2025-01-21)

  • chore: no changes.

0.5.3 (2025-01-21)

  • fix: duplication of recently installed extensions in search results.
  • fix: add information and error notifications when updating and removing an extension.
  • refactor: add showLogsCommand() function to display a link to the output log in the notification.

0.5.2 (2025-01-19)

  • fix: add source after updating an extension.
  • refactor: add installQuartoExtensionSource to contain the logic to install an extension and add the source.

0.5.1 (2025-01-19)

  • fix(.vscodeignore): remove wrong entry.

0.5.0 (2025-01-19)

  • feat: add view to display and to manage the Quarto extensions installed.
  • feat(checkQuartoPath): better check for the Quarto CLI path.
  • refactor(utils/extensions.ts): externalise user prompts to a separate module (utils/ask.ts).
  • refactor: update and correct trust authors and confirm installations prompts option value, i.e., Yes, always trust.
  • refactor(extension.ts): don’t use temporary variables for commands.

0.4

0.4.2 (2025-01-05)

  • feat: add command Quarto Wizard: New Reproducible Document to create a new Quarto document in “new File” menu.
  • refactor: use “category” instead of hardcoding Quarto Wizard: in the command title.

0.4.1 (2025-01-04)

  • feat(assets/templates): add bibliography reference to the templates.

0.4.0 (2025-01-04)

  • feat(README.md): add usage instructions for Quarto Wizard: New Reproducible Document.
  • feat: add settings to specify the Quarto CLI path (quartoWizard.quarto.path).
  • feat: add settings to control user prompts for trusting authors and confirming installations (quartoWizard.ask.trustAuthors, quartoWizard.ask.confirmInstall).
  • feat: introduce prompts for users to trust authors and confirm installations, with a “Never ask again” option to update settings accordingly.
  • feat: enhance the extension installation process to update _extension.yml with the source repository (i.e., source: <repository>), ensuring future updates.
  • fix(README.md): remove duplicated command prefix.
  • style: format code with Prettier.
  • ci: allow anything after version number header in CHANGELOG.md.

0.3

0.3.0 (2024-11-19)

  • feat: add command Quarto Wizard: New Reproducible Document to create a new Quarto document. (#6)
  • refactor: replace “see details” with “show logs” in notification messages. (#5)

0.2

0.2.1 (2024-11-18)

  • docs: update README.md with updated usage instructions.

0.2.0 (2024-11-18)

  • feat: cache the list of available Quarto extensions (CSV) for twelve hours.
  • feat: add command Quarto Wizard: Clear Recently Installed Extensions to remove the list of recently installed extensions.
  • fix: Quarto Wizard: Install Extension(s) errors if no workspace/folder is open. (#4)
  • refactor: split extension.ts into multiple files.
  • refactor: rename quartoExtensions to quartoWizard.
  • refactor: update commands prefix from Quarto to Quarto Wizard.
  • ci: publish to Open VSX Registry. (#3)

0.1

0.1.0 (2024-11-16)

  • Initial release of Quarto Wizard extension.
  • feat: add command Quarto: Install Extension(s) to open the extension installer interface.
  • feat: add command Quarto: Show Quarto Wizard Output to display the output log for the extension.
Back to top