Publishing

​

Packages: The Unit of Publishing

• .malloy files — semantic model definitions
• Data apps — dashboards and applications built on the model, shipped as a public/ directory of plain web files. A data app queries the package’s own models — with all access rules applied — and automatically appears in every workspace the package is added to
• Data files (CSV or Parquet) — embedded data published with the package (see Embedded Data)
• publisher.json — the package manifest

​

The Package Manifest

{
    "name": "ecommerce",
    "version": "0.0.1",
    "description": "ecommerce demo data",
    "explores": ["orders.malloy", "customer_health.malloy"],
    "queryableSources": "declared",
    "scope": "package",
    "materialization": { "freshness": { "window": "24h", "fallback": "live" } }
}

• Discovery — explores and queryableSources curate what agents and users see; see Curating Discovery on the Discovery page
• Serving policy — scope and materialization.freshness set how the package’s derived copies (materialized tables and search indexes) are reused across versions and how fresh they’re kept; see Performance & Cost

​

How to Publish

• In the Credible App — ask the agent to publish your draft. It packages the draft, deploys it to your environment, and confirms the published version. See Build & Publish.
• In your IDE — type /credible-publish in your agent’s chat. The agent creates a publisher.json if needed, bumps the version on a republish (versions are immutable), and runs the publish for you.
• With the CLI directly:
  npm i -g @credibledata/cred-cli   # install (once)
  cred login <organizationName>     # authenticate (once)
  cred set environment <environmentName>
  cd /path/to/your/package
  cred publish --set-latest
  
  The --set-latest flag promotes the version to the package’s “latest” immediately, before its indexes and materialized tables are built. You can usually omit it: with auto-promote (on by default), the new version is promoted automatically once it’s fully built and ready to serve. See the CLI page for all commands.
• From CI/CD — automate publishing when changes merge to Git. A GitHub Actions workflow versions and publishes the package on every merge, so your main branch is always what’s served. See CI/CD Setup.

​

What Happens When You Publish

1. Validate and version. The service compiles the model and creates a new immutable version of the package. Model errors and publish-time guardrails (like the indexed-dimension rules) surface here — as publish errors, not silent wrong answers downstream.
2. Build derived copies. Every #@ persist source is materialized and every #(index) dimension gets its search index built, sequenced so an index derives from the materialized table it depends on. From then on, the platform keeps these copies fresh on your declared objectives. See Performance & Cost.
3. Index for retrieval. The Credible Context Engine indexes your model’s dimensions, measures, views, #(doc) descriptions, and #(index) values — this is what lets agents find and understand your data. Indexing typically takes around 10 minutes.
4. Wire up enforcement. Your #(authorize) gates and secure givens are enforced on every query against the served version, identically across every consumer — workspace chat, MCP agents, dashboards, data apps, and APIs.

​

Serving and Version Management

• One pinned “latest”. One version is designated as latest — the default served to consumers who don’t specify a version. Consumers on “latest” automatically pick up updates when the pin moves; consumers that need stability (like a production dashboard) can pin to a specific version.
• Versions remain available. Published versions are preserved, enabling rollbacks, pinned production deployments, gradual adoption across teams, and historical audits.

​

Auto-Promote

• Rollbacks stick. Auto-promote only promotes a version that has never been latest. If you roll back by re-pinning an older version, the platform won’t fight you and re-pin the newer one.
• No going backward. A version that’s ready but older than the current latest isn’t promoted.

​

Auto-Archive

​

Viewing Published Versions

• Credible App at https://your-org.app.credibledata.com — navigate to your environment and click a package to see complete version history, pin or unpin versions, check build and indexing status, and view package metadata
• Credible CLI — list a package’s versions from the command line:
  cred ls versions <packageName>
  

​

Next Steps