Tags

Tags give the ability to mark specific points in history as being important
  • v0.3.0

    Release: @dunn.dev/reference v0.3.0
    v0.3.0 — promote converged estate site chrome into site.css
    
    CTA button pair, 2-col tile card grid + install list, paper-card diagram
    frame, hero tagline; --text-md token. Estate sites consume this instead
    of vendoring forks. Additive, non-breaking.
  • 0.2.0

    Release: @dunn.dev/reference 0.2.0
    0.2.0
    
    Three new standards + CI uplift to dunn.dev/pipeline 2.3.0:
    
    - container-publishing: Containerfile FROM uses ci-runtime-go|node
      catalog base; .gitlab-ci.yml uses container-image@X.Y.Z catalog
      include.
    - package-publishing: any publish-shaped CI also includes slsa-attest
      + release-create.
    - image-cleanup: container_expiration_policy.enabled at project level.
    
    Reference's own CI now publishes @dunn.dev/reference via catalog
    node-publish + node-sbom + slsa-attest + release-create. Tarball
    cosign sign-blob; SBOM + SLSA v1.0 attest attach to the GitLab
    Release.
  • 0.1.0

    0.1.0 — initial publish
    
    First release of @dunn.dev/reference. Folds in everything design.dunn.dev
    used to publish (tokens, chrome, mark, journal) plus reference's own
    contracts (repository, pipeline, design-system) and their templates.
    
    Exports map:
      tokens/index.css, colors.css, typography.css, spacing.css, motion.css
      tokens/colors.json, typography.md
      site.css, mark/*, journal/{JournalRail.astro, journal-base.css, types}
      repository/templates/*
    
    Consumers in the dunn.dev group can install via the project's GitLab
    npm registry. CI_JOB_TOKEN handles auth within the group; locally,
    configure .npmrc with a personal access token.