Skip to content

Releases: jakegold1647/sam-doctor

SAM Doctor v0.7.7

Choose a tag to compare

@github-actions github-actions released this 03 Aug 20:46

SAM Doctor v0.7.7

SAM Doctor v0.7.7 adds a focused diagnosis for Lambda container-image deployments
that fail because Lambda cannot access the configured Amazon ECR image.

  • Install the CLI with python -m pip install sam-doctor.
  • Use the Marketplace Action with jakegold1647/sam-doctor@v0.7.7.
  • Use --fail-on-findings only when a supported diagnosis should fail a CI job.
  • Reports remain local, redacted, and evidence-first.

SAM Doctor v0.7.6

Choose a tag to compare

@github-actions github-actions released this 03 Aug 18:39

SAM Doctor v0.7.6

SAM Doctor v0.7.6 packages the latest tested diagnostics and keeps the CLI,
Marketplace Action, site, and release links on the same stable version.

  • Install the CLI from the attached GitHub wheel or from PyPI.
  • Use the Marketplace Action with jakegold1647/sam-doctor@v0.7.6.
  • Use --fail-on-findings only when a supported diagnosis should fail a CI job.
  • Reports remain local, redacted, and evidence-first.

SAM Doctor v0.7.5

Choose a tag to compare

@github-actions github-actions released this 03 Aug 17:55

SAM Doctor v0.7.5

SAM Doctor v0.7.5 is the first stable release of the polished local CLI and
GitHub Action path.

  • Install the CLI from PyPI with python -m pip install sam-doctor.
  • Use the Marketplace Action with jakegold1647/sam-doctor@v0.7.5.
  • Run sam-doctor demo locally before connecting it to a deployment workflow.
  • Reports remain local, redacted, and evidence-first.

SAM Doctor v0.7.5-rc.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Aug 17:51

SAM Doctor v0.7.5-rc.1

This prerelease puts the polished first-use path on one tested version:

  • The README and project site install the matching wheel directly from GitHub.
  • The Marketplace Action examples run after failed deployments and use
    if: always() so the diagnostic report is not skipped.
  • Human-readable no-match reports point users toward sanitized rule feedback.
  • Scheduled launch monitoring no longer treats the intentional prerelease state
    as a failed stable-release check.
  • Outreach summaries include an ethical growth score and concrete next actions.

The CLI and Action remain local and evidence-first: they do not access AWS,
upload logs, or change resources.

SAM Doctor v0.7.4

Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Aug 04:23

SAM Doctor v0.7.4

SAM Doctor v0.7.4 gives the composite GitHub Action a distinct Marketplace
display name: SAM Doctor AWS Deployment Diagnostics. The action interface,
redaction behavior, and opt-in failure gating are unchanged.

SAM Doctor v0.7.3

SAM Doctor v0.7.3 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Aug 04:10

SAM Doctor v0.7.3

SAM Doctor v0.7.3 packages Marketplace metadata with the composite GitHub
Action. The listing uses the action's existing description plus an activity
icon and yellow branding, while keeping its redacted summaries and optional
failure gating unchanged.

This release also refreshes the diagnostic issue form so contributors provide
their installed version rather than copying a stale placeholder.

SAM Doctor v0.7.2

SAM Doctor v0.7.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Aug 04:04

SAM Doctor v0.7.2

SAM Doctor v0.7.2 extends report redaction to the displayed source filename.
Account IDs, email addresses, AWS identifiers, and supported token formats are
now protected consistently in terminal, Markdown, and JSON reports.

The tool remains local-only and continues to redact only supported patterns;
review reports before sharing them outside your team.

SAM Doctor v0.7.1

SAM Doctor v0.7.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Aug 04:01

SAM Doctor v0.7.1

SAM Doctor v0.7.1 makes multi-finding reports follow the order of the source
log. Earlier supported failures now appear before downstream rollback and
deployment noise, making the report easier to investigate in the same sequence
as the failed operation.

This is a focused compatibility release: the rule catalog, local-only behavior,
and redaction model are unchanged.

SAM Doctor v0.7.0

SAM Doctor v0.7.0 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Aug 03:55

SAM Doctor v0.7.0

SAM Doctor v0.7.0 extends the evidence-first catalog with five direct service
errors drawn from sanitized public deployment reports.

Highlights

  • Detects invalid SAM property keys and IAM role trust policies that contain a
    prohibited Resource field.
  • Detects Lambda container-image/code-signing incompatibility and invalid S3
    bucket names.
  • Detects the S3 GetObject denial that prevents CloudFormation from creating a
    Lambda layer from its artifact.

Each report keeps the scope narrow: it identifies the service error and provides
safe verification steps, without accessing AWS or changing a resource.

SAM Doctor v0.6.0

SAM Doctor v0.6.0 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Aug 03:52

SAM Doctor v0.6.0

SAM Doctor v0.6.0 makes it easier to use the local diagnostic in GitHub Actions
without hand-writing an installation or report-parsing step.

Highlights

  • Adds a composite GitHub Action: jakegold1647/sam-doctor@v0.6.0.
  • Exposes finding-count and has-findings workflow outputs.
  • Keeps Markdown job summaries and failure gating opt-in, so a workflow author
    chooses when diagnostics should be surfaced or fail a job.
  • Adds high-confidence diagnosis for four public deployment signals: missing
    esbuild, conflicting --resolve-s3 and --s3-bucket settings, API Gateway
    deployments with no methods, and initial stacks left in ROLLBACK_COMPLETE.

The action analyzes only the log file supplied by the workflow. Its summary
contains matched, redacted evidence rather than the full input log; review it
before sharing a workflow run outside your team.