Repository navigation
Releases: bcgov/crow
Release list
BCGov Crow - v0.12.4
BCGov Crow - v0.12.4
Release type
Patch release
Summary
Crow Testing makes property-based test failures easier to replay while keeping
normal runs exploratory. It also clarifies how project-specific feature
scenarios and recurring manual checks are organized and reviewed.
Highlights
- CsCheck examples use a per-test
ReplaySeedlocal to replay a reported
failure in isolation; a trailing guard catches seeds accidentally left in
normal tests. - Scenario planning follows confirmed application and feature ownership.
Manual QA guidance keeps a single browse/release index with linked,
tester-facing checks and explicit review status.
Changes
- Documented how to reproduce a failed property test in Test Explorer or with
a filteredCsCheck_Seedrun, and how to retain the discovered case as a
regression test without narrowing future exploratory runs. - Clarified the nullable-reference prerequisite, the
CsCheck_Timeoverride,
and the intentionally relative date generators in the .NET testing guidance. - Aligned scenario-organization and manual-QA templates with stable check IDs,
application/page-specific index links, and approval rules for existing
manual details.
Validation
- Crow asset validation: Passed with 0 errors and 0 warnings.
- Package dry run: Passed; 222 files selected.
- Archive inspection: Not run; no release archive has been generated for this draft.
- Additional checks: Crow release guards, PR version checks, reviewed-note
candidate tests, andgit diff --checkpassed.
Artifacts
- Archive:
bcgov-crow-0.12.4.zip - SHA-256 file:
bcgov-crow-0.12.4.zip.sha256 - SHA-256:
aced24f31a02adf5b921102fdf9753e70450f9ec728f133ee62737250d1b3c56
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.12.4 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.12.4.zip --global --target copilotBCGov Crow - v0.12.3
BCGov Crow - v0.12.3
Release type
Patch release
Summary
Crow Testing now organizes feature scenarios around each repository's own
application structure and provides manual QA guidance that is easier to review,
browse, and run.
Highlights
- Scenario planning uses evidence-based, reviewer-confirmed feature homes and
ownership gates, avoiding unapproved category creation or document moves. - Manual QA guidance provides one browse and release index linked to
tester-focused checks with reproducible setup, visible outcomes, and
supporting technical details. - AI-authored manual details start as Draft. Approved details remain unchanged
unless a reviewer authorizes a named-document change, which returns the
content to Draft for review.
Changes
- Added guidance and a template for deriving and confirming project-specific
scenario organization, including ownership decisions and cross-application
feature homes. - Aligned the Crow Testing agent, skill, workflow, and scenario templates with
the new organization and manual-document review rules. - Reworked manual QA templates to separate the browse index from runnable
checks, use stable check identifiers, and keep technical traceability below
tester-facing instructions.
Validation
- Crow asset validation: Passed — 0 errors, 0 warnings.
- Package dry run: Passed — 222 files selected; no archive was generated.
- Archive inspection: Not run — no release archive was generated for this draft.
- Additional checks: Version alignment, Crow version/release guard tests,
reviewed-note candidate workflow tests, andgit diff --checkpassed.
Artifacts
- Archive:
bcgov-crow-0.12.3.zip - SHA-256 file:
bcgov-crow-0.12.3.zip.sha256 - SHA-256:
6e45954721b9aa6398d947d832f59bb3a0519f9077f4604f051d2293caf715ca
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.12.3 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.12.3.zip --global --target copilotBCGov Crow - v0.12.2
BCGov Crow - v0.12.2
Release type
Patch release
Summary
Crow's Raven setup catalog now reflects Raven v0.2.0, and Windows setup
cleanup handles process-exit races without masking failures when processes
remain active.
Highlights
- The reviewed catalog now matches Raven v0.2.0 package versions across all
17 servers while preserving their existing launchers and access levels. - Windows setup cleanup treats a
taskkillerror as a race only after
confirming that the root process and every reported process have exited.
Errors remain visible when any affected process is still running.
Changes
- Updated Raven's reviewed server catalog to package version 0.2.0.
- Clarified that Raven's pre-stable contract began at version 0.1.0.
Validation
- Crow asset validation: Passed — 0 errors, 0 warnings.
- Package dry run: Passed — 220 files selected; the existing plugin manifest
was retained. - Archive inspection: Not run — no release archive was generated for this
draft. - Additional checks: Raven setup tests passed (42 passed, 0 failed);
node --checkpassed for the setup script and tests;git diff --check
passed.
Artifacts
- Archive:
bcgov-crow-0.12.2.zip - SHA-256 file:
bcgov-crow-0.12.2.zip.sha256 - SHA-256:
c073ef0a402844cd9e1f71adfa4ee003b4bc2375f00861ea8cf3bb3689bcfbbf
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.12.2 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.12.2.zip --global --target copilotBCGov Crow - v0.12.1
BCGov Crow - v0.12.1
Release type
Patch release
Summary
The Crow Raven Setup Agent now prepares local SonarQube scanners when Sonar
MCP is active, configured, or selected during setup. It covers the generic
SonarScanner CLI and the .NET/MSBuild scanner, checks official stable releases
during setup and maintenance, and requires confirmation before installation
or upgrades.
Highlights
- Sonar MCP detection covers the active
sonar_run_scantool, Raven's
sonarserver ID, standalonesonar-mcpconfiguration, and selecting
sonarduring a new setup. - The agent installs the generic scanner into a versioned user-local
directory and manages the .NET scanner as an exact-version global tool when
a compatible .NET SDK is available. - Installation and updates preview paths, environment changes, integrity
checks, and rollback steps. Missing SDKs, unknown server compatibility, and
unverifiable MCP process visibility are reported rather than treated as
successful setup. - Scanner releases are checked when the Raven Setup Agent is invoked for
setup or maintenance. The optional Copilot update hook does not track
scanner releases, and updates are never applied without confirmation.
Changes
- Added conditionally loaded SonarScanner setup, verification, update, and
rollback guidance to the Raven setup skill. - Updated the Raven Setup Agent, package documentation, collection
installation references, and manifests for Crow v0.12.1.
Validation
- Crow asset validation: Passed — 0 errors, 0 warnings.
- Independent non-GPT model reviews: Passed — no remaining material findings.
- APM package dry run: Passed — 220 files selected. Version alignment check
was skipped because the package has no marketplace block. git diff --check: Passed.
Artifacts
- Archive:
bcgov-crow-0.12.1.zip - SHA-256 file:
bcgov-crow-0.12.1.zip.sha256 - SHA-256:
7f4b5bd97b4d1b3a9bc967296ebcd667391f4914664f81790a8625ada18b12e3
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.12.1 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.12.1.zip --global --target copilotBCGov Crow - v0.12.0
BCGov Crow - v0.12.0
Release type
Minor release
Summary
Crow separates routine framework and dependency maintenance from security
remediation with a dedicated update agent and focused skills included in the
Starter Package and full Crow package.
Highlights
- The Crow Framework & Dependency Update Agent supports framework/runtime,
third-party dependency, and combined update scopes without requiring
security-review reports or ticket workflows. - Scheduled or unattended runs are limited to supported, non-breaking
patch/minor updates, defer components without baseline verification, and
restore a failed component after verification; migrations needing human
decisions are reported and deferred. Crow does not configure a scheduler. - Security Remediation retains its existing framework and dependency scopes
as deprecated compatibility routes through the new skills, while verified
security findings remain in the security-remediation workflow. - Security-ticket scopes run applicable vulnerability remediation, hardening,
and test work only for findings in the validated ticket backlog. - The dependency-update skill routes inventories through a technology-grouped
package-manager catalog and supports ecosystems without lockfiles when the
selected manager and repository policy do not require one. - Pull-request asset validation checks local links, skill-routing dependencies,
and whether each collection bundles the transitive skills and modules used by
its agents.
Changes
- Added
crow-framework-updatesandcrow-dependency-updatesskills with
evidence, compatibility, manager-specific lockfile, advisory-check, and
verification guidance. - Added a package-manager inventory and routing module covering application
ecosystems, infrastructure, containers, and non-standard inputs. - Included the agent and skills in the Starter Package, and updated the
Security Remediation collection for the deprecated compatibility routes. - Added a dependency-graph check and regression tests to the Crow asset
validator; both collections now include the project-context
technology-preferences module they conditionally use. - Updated ticket-scope gates, known-skill routing, module-only dependency
handling, and repository-root link validation. - Updated package discovery metadata, collection manifests, installation
examples, and links for Crow v0.12.0.
Validation
- Crow asset validation: Passed — 0 errors, 0 warnings.
- Dependency-graph and Security Remediation scope regression tests: Passed.
- PowerShell lint: Passed for changed scripts.
- Package dry run: Passed — 219 files.
- Archive inspection: Required before draft publication.
- Additional checks: Release-draft and package-version guard tests passed;
git diff --checkpassed. Sonar quality gate: Passed, with 0 new issues;
the generic scanner did not analyze C# files.
Artifacts
- Archive:
bcgov-crow-0.12.0.zip - SHA-256 file:
bcgov-crow-0.12.0.zip.sha256 - SHA-256:
b6b3b538eca64732f95efdea7a1bb841860c924973505d12c355456cd56b7cec
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.12.0 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.12.0.zip --global --target copilotBCGov Crow - v0.11.5
BCGov Crow - v0.11.5
Release type
Patch release
Summary
Crow solution architecture engagements can remember a person's technology
preferences across projects without treating past choices as team policy or
overriding current solution constraints.
Highlights
- User-local, dated technology preferences are considered during interactive
solution design and saved only after permission for each choice. - Preferences cover application technologies as well as identity, integration,
operations, data-adjacent capabilities, and delivery practices. - Pull requests that change release-relevant package assets must propose a
package version higher than the base branch before merging.
Changes
- Added a user-local technology-preferences CLI with validation and commands
to list, remember, and forget context-specific preferences. - Updated the solution-architecture workflow to distinguish personal
preferences from evidence, constraints, and approved decisions. - Added a pre-merge version check for changes under
.apm/, collections, or
apm.yml, along with regression tests.
Validation
- Crow asset validation: Passed - 0 errors, 0 warnings.
- Package dry run: Passed - 212 files.
- Archive inspection: Required before draft publication.
- Additional checks: Preference-memory and release-version regression tests
passed; release validation remains required before publication.
Artifacts
- Archive:
bcgov-crow-0.11.5.zip - SHA-256 file:
bcgov-crow-0.11.5.zip.sha256 - SHA-256:
1c4df79d5d48bdc90db7c89dbb7cf7dbb30dc549de9abfc64031e5cedc8374c0
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.11.5 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.11.5.zip --global --target copilotBCGov Crow - v0.11.4
BCGov Crow - v0.11.4
Release type
Patch release
Summary
Crow adds conditional architecture and development guidance for reviewable
decisions affecting people, responsible handling of information throughout its
lifecycle, and continuity when a service operates across channels.
Highlights
- Architecture and development workflows now consider how consequential
automated decisions can be explained, challenged, reviewed, and corrected. - Architecture documents can distinguish primary and derived information
stores, processing locations, retention authority, and correction paths
without assuming approvals that have not been established. - Multi-channel service designs can account for shared case state, authorized
resumption, and confirmation of lawfully reusable information.
Changes
- New conditionally routed service-responsibilities guidance and corresponding
prompts in the solution architecture and architecture review templates.
Validation
- Crow asset validation: Passed - 0 errors, 0 warnings.
- Package dry run: Passed - 207 files.
- Archive inspection: Passed - 207 entries, including the new guidance module;
no evidence or session-state paths. - Additional checks: Architecture and solution architecture output validator
tests and release guards passed.
Artifacts
- Archive:
bcgov-crow-0.11.4.zip - SHA-256 file:
bcgov-crow-0.11.4.zip.sha256 - SHA-256:
20e087894c316dda507fdd59e73085ae893cbaffd28436e0126e1ae01a502ccd
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.11.4 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.11.4.zip --global --target copilotBCGov Crow - v0.11.3
BCGov Crow - v0.11.3
Release type
Patch release
Summary
Crow adds security-control assurance checks that tests
cited as evidence actually exercise production controls rather than
reproducing their behavior inside the test.
Highlights
- Security-control assurance traces a cited test's actions and assertions to
its production enforcement point, including calls made through helpers,
mocks, and callbacks. - Tests that perform a cleanup or authorization sequence themselves no longer
count as evidence that the production control works.
Changes
- Security-relevant data retention, deletion, and credential revocation are
explicit control-assurance review targets. - Reviewers consider other valid tests before reporting a coverage gap and
hand replacement-test requirements to the testing workflow.
Validation
- Crow asset validation: Passed - 0 errors, 0 warnings.
- Package dry run: Passed - 206 files.
- Archive inspection: Passed - 206 entries, including the
updated security review assets; no evidence or session-state paths. - Additional checks: Security review synthesis and release draft tests passed;
Sonar quality gate passed with 0 new-code issues (the generic scanner does
not analyze bundled C# examples).
Artifacts
- Archive:
bcgov-crow-0.11.3.zip - SHA-256 file:
bcgov-crow-0.11.3.zip.sha256 - SHA-256:
e16fcb99270f68e4ef0aa61216048d9fc1fdffd939827375dea976c07ec84c2f
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.11.3 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.11.3.zip --global --target copilotBCGov Crow - v0.11.2
BCGov Crow - v0.11.2
Release type
Patch release
Summary
Crow extends its existing technology-routed architecture, development, testing,
and security review skills with Java guidance.
Highlights
- Java architecture and development modules cover modern JDK choices, HTTP
applications, safe persistence, builds, CI, and operational readiness. - Container-specific guidance distinguishes embedded and external Tomcat,
Jetty, Undertow, and Jakarta EE application servers and their enabled profiles. - Java unit and integration testing guidance covers JUnit Jupiter, real HTTP
boundaries, database semantics, and deployed WAR verification.
Changes
- Skill routers load Java modules only for relevant Java projects and tasks.
- Existing skills, agent names, and output contracts remain unchanged.
Validation
- Crow asset validation: Passed - 0 errors, 0 warnings.
- Package dry run: Passed - 206 files; Java modules included.
- Archive inspection: Passed - 206 entries, including all 10 Java modules;
no evidence or local-state paths. - Additional checks: Crow release draft tests passed; Sonar quality gate
passed with 0 new-code issues (generic scanner cannot analyze bundled C#
examples); two independent model reviews completed and material findings
incorporated.
Artifacts
- Archive:
bcgov-crow-0.11.2.zip - SHA-256 file:
bcgov-crow-0.11.2.zip.sha256 - SHA-256:
ee4383b41c0a2972b7e112912a826dcbc679643d48e9e6bb16098a709fe1bcc0
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.11.2 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.11.2.zip --global --target copilotBCGov Crow - v0.11.1
BCGov Crow - v0.11.1
Release type
Patch release
Summary
Crow adds an opt-in daily update reminder during Copilot agent use and a
release-maintained APM update track, without scheduled tasks or automatic
upgrades.
Highlights
- The Raven Setup Agent offers an optional user-level Copilot hook once.
After consent, it checks Crow's stable release and any bundled Raven or
codebase-memory-mcp release recorded by Crow Setup during prompt activity at
most once every 24 hours. An unavailable release source does not suppress
updates found elsewhere; failed checks retry after about one hour. Updates
are never installed automatically. - A release-maintained
stablebranch lets global APM installs follow
published stable Crow releases. It is seeded after successful main-branch
asset validation and advances only after a stable release is published.
Exact-tag installations remain fixed until migrated.
Changes
- Raven freshness checks now record their 24-hour timestamp only after APM
checks succeed, so a failed check remains eligible for retry. - Setup guidance explains exact-tag APM behavior and how to migrate to
#stable. Install documentation retains version-pinned options, and both
collections now declare the 0.11.1 package version and dependency refs.
Validation
- Crow asset validation: Passed — 0 errors, 0 warnings.
- Package dry run: Passed — 196 files.
- Archive inspection: Passed — 196 entries; no evidence or local-state paths.
- Additional checks: Raven setup tests passed (40/40); Crow release guard tests
passed; stable-branch workflow YAML parsing and PSScriptAnalyzer passed. The
prior branch Sonar scan found no new issues, but its quality gate did not
pass because coverage was 0.0% against a 10% threshold; exact release-commit
Sonar validation remains outstanding.
Artifacts
- Archive:
bcgov-crow-0.11.1.zip - SHA-256 file:
bcgov-crow-0.11.1.zip.sha256 - SHA-256:
7810376418d7298da179bddf327670a7cd4da63c5d4ef116e01ea6aab1554a95
Installation
Install the tagged release globally:
apm install bcgov/crow#v0.11.1 --global --target copilotOr install the packaged archive:
apm install .\build\bcgov-crow-0.11.1.zip --global --target copilot