dlake 0.5.28

dlake release notes

0.5.28 (2026-08-29)

• Tool listings now tell you what your key can actually use. The Help and
  API guides, the CLI reference and the dlake agent skill no longer quote a
  fixed number of admin or data-plane tools: what is available depends on the
  key you are signed in with, so dlake admin list and dlake tool list are
  the answer — run either one to see your own surface.
• Both npm packages now link to the product overview from their README and
  registry page.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.27 (2026-08-27)

• New agent skill: dlake-crmpro-hubspot. The HubSpot specifics of a CRMPro
  forward sync, in one place: the configuration a HubSpot process needs, what its
  source view must provide, the seed-then-upsert pair that lets some fields stay
  CRM-owned while the rest follow the ERP, the field-list rows an object needs
  before it will push anything, and the checks to run when a sync finishes
  without writing records. Read it with
  dlake skills show dlake-crmpro-hubspot, or install all nine with
  dlake skills install.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.26 (2026-08-27)

• The Sync Agent guidance now states that available commands vary by agent
  build: try a command as written, and where a build prompts instead of
  accepting a flag, work through it interactively — --help on that machine
  is the authority on the form it takes.
• The db_owner requirement for the Normal Sync source login is now in the
  Help and CLI guides as well as the agent skills.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.25 (2026-08-27)

• Normal Sync and CRMPro guidance, considerably expanded. The agent skills
  now spell out what a CRMPro source view has to contain and how to build one
  that syncs — the identity and change-detection joins, key formats, process
  naming, and the value rules each destination CRM enforces (currency codes,
  email addresses, dates). Reading dlake skills show dlake-crmpro before
  building a process is now the short path.
• The Normal Sync guidance states the source SQL login needs db_owner on the
  ERP database, and why a read-only login passes the connection test but
  cannot sync.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.24 (2026-08-26)

• New: Normal Sync resync. dlake normalsync resync --confirm asks the
  on-premises agent to re-pull every synced table on its next run;
  --table <name> queues a single table (SYSPRO custom tables like
  ArCustomer+ are fully supported), and --clear discards the queued list.
  Nothing is deleted or dropped — the agent does the work.
• New: dlake normalsync resync-status. Shows what is queued, plus clone
  coverage: the rows actually present in each clone table against the count
  recorded at the last sync — the quickest way to see whether a sync actually
  moved data, per table.
• The same operations are available to AI agents as four new admin tools, and
  the Normal Sync guide and skills cover them. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.23 (2026-08-26)

• Documentation refresh: the npm package README now describes all eight bundled
  agent skills, including dlake-syncagent.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.22 (2026-08-25)

• Clearer package listing on npm: @commercient/dlake now opens by describing
  what the CLI and the platform actually do, with a first-run example, rather
  than starting with installer internals. Both packages also carry a fuller set
  of keywords, so the CLI is easier to find when searching npm for ERP and CRM
  integration, sync, and SQL Server tooling.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.21 (2026-08-25)

• New agent skill: dlake-syncagent. Installing and configuring the
  Commercient Sync Agent — the Windows agent that runs on your own ERP server and
  actually reads your source data. Covers signing in, listing your licensed
  products, installing one, configuring it per product type, testing the
  connection, and reading the agent's health, using the scriptable
  CommercientSyncAgentCLI.exe. It is the on-premises companion to the existing
  skills, which cover the platform side. Read it with
  dlake skills show dlake-syncagent, or install all of them with
  dlake skills install.
• The Help guide and the CLI reference gained a Sync Agent section covering the
  same ground, including the install-and-test sequence and the exit codes worth
  branching on in a script. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is t...
  

dlake 0.5.27

dlake release notes

0.5.27 (2026-08-27)

• New agent skill: dlake-crmpro-hubspot. The HubSpot specifics of a CRMPro
  forward sync, in one place: the configuration a HubSpot process needs, what its
  source view must provide, the seed-then-upsert pair that lets some fields stay
  CRM-owned while the rest follow the ERP, the field-list rows an object needs
  before it will push anything, and the checks to run when a sync finishes
  without writing records. Read it with
  dlake skills show dlake-crmpro-hubspot, or install all nine with
  dlake skills install.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.26 (2026-08-27)

• The Sync Agent guidance now states that available commands vary by agent
  build: try a command as written, and where a build prompts instead of
  accepting a flag, work through it interactively — --help on that machine
  is the authority on the form it takes.
• The db_owner requirement for the Normal Sync source login is now in the
  Help and CLI guides as well as the agent skills.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.25 (2026-08-27)

• Normal Sync and CRMPro guidance, considerably expanded. The agent skills
  now spell out what a CRMPro source view has to contain and how to build one
  that syncs — the identity and change-detection joins, key formats, process
  naming, and the value rules each destination CRM enforces (currency codes,
  email addresses, dates). Reading dlake skills show dlake-crmpro before
  building a process is now the short path.
• The Normal Sync guidance states the source SQL login needs db_owner on the
  ERP database, and why a read-only login passes the connection test but
  cannot sync.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.24 (2026-08-26)

• New: Normal Sync resync. dlake normalsync resync --confirm asks the
  on-premises agent to re-pull every synced table on its next run;
  --table <name> queues a single table (SYSPRO custom tables like
  ArCustomer+ are fully supported), and --clear discards the queued list.
  Nothing is deleted or dropped — the agent does the work.
• New: dlake normalsync resync-status. Shows what is queued, plus clone
  coverage: the rows actually present in each clone table against the count
  recorded at the last sync — the quickest way to see whether a sync actually
  moved data, per table.
• The same operations are available to AI agents as four new admin tools, and
  the Normal Sync guide and skills cover them. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.23 (2026-08-26)

• Documentation refresh: the npm package README now describes all eight bundled
  agent skills, including dlake-syncagent.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.22 (2026-08-25)

• Clearer package listing on npm: @commercient/dlake now opens by describing
  what the CLI and the platform actually do, with a first-run example, rather
  than starting with installer internals. Both packages also carry a fuller set
  of keywords, so the CLI is easier to find when searching npm for ERP and CRM
  integration, sync, and SQL Server tooling.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.21 (2026-08-25)

• New agent skill: dlake-syncagent. Installing and configuring the
  Commercient Sync Agent — the Windows agent that runs on your own ERP server and
  actually reads your source data. Covers signing in, listing your licensed
  products, installing one, configuring it per product type, testing the
  connection, and reading the agent's health, using the scriptable
  CommercientSyncAgentCLI.exe. It is the on-premises companion to the existing
  skills, which cover the platform side. Read it with
  dlake skills show dlake-syncagent, or install all of them with
  dlake skills install.
• The Help guide and the CLI reference gained a Sync Agent section covering the
  same ground, including the install-and-test sequence and the exit codes worth
  branching on in a script. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need `-...

dlake 0.5.26

dlake release notes

0.5.26 (2026-08-27)

• The Sync Agent guidance now states that available commands vary by agent
  build: try a command as written, and where a build prompts instead of
  accepting a flag, work through it interactively — --help on that machine
  is the authority on the form it takes.
• The db_owner requirement for the Normal Sync source login is now in the
  Help and CLI guides as well as the agent skills.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.25 (2026-08-27)

• Normal Sync and CRMPro guidance, considerably expanded. The agent skills
  now spell out what a CRMPro source view has to contain and how to build one
  that syncs — the identity and change-detection joins, key formats, process
  naming, and the value rules each destination CRM enforces (currency codes,
  email addresses, dates). Reading dlake skills show dlake-crmpro before
  building a process is now the short path.
• The Normal Sync guidance states the source SQL login needs db_owner on the
  ERP database, and why a read-only login passes the connection test but
  cannot sync.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.24 (2026-08-26)

• New: Normal Sync resync. dlake normalsync resync --confirm asks the
  on-premises agent to re-pull every synced table on its next run;
  --table <name> queues a single table (SYSPRO custom tables like
  ArCustomer+ are fully supported), and --clear discards the queued list.
  Nothing is deleted or dropped — the agent does the work.
• New: dlake normalsync resync-status. Shows what is queued, plus clone
  coverage: the rows actually present in each clone table against the count
  recorded at the last sync — the quickest way to see whether a sync actually
  moved data, per table.
• The same operations are available to AI agents as four new admin tools, and
  the Normal Sync guide and skills cover them. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.23 (2026-08-26)

• Documentation refresh: the npm package README now describes all eight bundled
  agent skills, including dlake-syncagent.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.22 (2026-08-25)

• Clearer package listing on npm: @commercient/dlake now opens by describing
  what the CLI and the platform actually do, with a first-run example, rather
  than starting with installer internals. Both packages also carry a fuller set
  of keywords, so the CLI is easier to find when searching npm for ERP and CRM
  integration, sync, and SQL Server tooling.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.21 (2026-08-25)

• New agent skill: dlake-syncagent. Installing and configuring the
  Commercient Sync Agent — the Windows agent that runs on your own ERP server and
  actually reads your source data. Covers signing in, listing your licensed
  products, installing one, configuring it per product type, testing the
  connection, and reading the agent's health, using the scriptable
  CommercientSyncAgentCLI.exe. It is the on-premises companion to the existing
  skills, which cover the platform side. Read it with
  dlake skills show dlake-syncagent, or install all of them with
  dlake skills install.
• The Help guide and the CLI reference gained a Sync Agent section covering the
  same ground, including the install-and-test sequence and the exit codes worth
  branching on in a script. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need --confirm, and the command stops before
  doing anything if it is missing. Two of those are worth the extra keystroke:
  the table register is shared by everyone using the same ERP and nothing can
  remove an entry from it, and a row filter is run against your ERP database by
  the on-premises agent exactly as you wrote it.

• The same operations are still available in full. Every verb has a longer
  form as dlake admin normalsync_<name>, with --help for its arguments;
  dlake admin list names them.

• Normal Sync commands need the Admin role. The API key has to belong to a
  user who holds Admin on the tenant. If it ...

dlake 0.5.25

dlake release notes

0.5.25 (2026-08-27)

• Normal Sync and CRMPro guidance, considerably expanded. The agent skills
  now spell out what a CRMPro source view has to contain and how to build one
  that syncs — the identity and change-detection joins, key formats, process
  naming, and the value rules each destination CRM enforces (currency codes,
  email addresses, dates). Reading dlake skills show dlake-crmpro before
  building a process is now the short path.
• The Normal Sync guidance states the source SQL login needs db_owner on the
  ERP database, and why a read-only login passes the connection test but
  cannot sync.
• Upgrade: npm install -g @commercient/dlake (or npm install -g datalake).

0.5.24 (2026-08-26)

• New: Normal Sync resync. dlake normalsync resync --confirm asks the
  on-premises agent to re-pull every synced table on its next run;
  --table <name> queues a single table (SYSPRO custom tables like
  ArCustomer+ are fully supported), and --clear discards the queued list.
  Nothing is deleted or dropped — the agent does the work.
• New: dlake normalsync resync-status. Shows what is queued, plus clone
  coverage: the rows actually present in each clone table against the count
  recorded at the last sync — the quickest way to see whether a sync actually
  moved data, per table.
• The same operations are available to AI agents as four new admin tools, and
  the Normal Sync guide and skills cover them. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.23 (2026-08-26)

• Documentation refresh: the npm package README now describes all eight bundled
  agent skills, including dlake-syncagent.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.22 (2026-08-25)

• Clearer package listing on npm: @commercient/dlake now opens by describing
  what the CLI and the platform actually do, with a first-run example, rather
  than starting with installer internals. Both packages also carry a fuller set
  of keywords, so the CLI is easier to find when searching npm for ERP and CRM
  integration, sync, and SQL Server tooling.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.21 (2026-08-25)

• New agent skill: dlake-syncagent. Installing and configuring the
  Commercient Sync Agent — the Windows agent that runs on your own ERP server and
  actually reads your source data. Covers signing in, listing your licensed
  products, installing one, configuring it per product type, testing the
  connection, and reading the agent's health, using the scriptable
  CommercientSyncAgentCLI.exe. It is the on-premises companion to the existing
  skills, which cover the platform side. Read it with
  dlake skills show dlake-syncagent, or install all of them with
  dlake skills install.
• The Help guide and the CLI reference gained a Sync Agent section covering the
  same ground, including the install-and-test sequence and the exit codes worth
  branching on in a script. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need --confirm, and the command stops before
  doing anything if it is missing. Two of those are worth the extra keystroke:
  the table register is shared by everyone using the same ERP and nothing can
  remove an entry from it, and a row filter is run against your ERP database by
  the on-premises agent exactly as you wrote it.

• The same operations are still available in full. Every verb has a longer
  form as dlake admin normalsync_<name>, with --help for its arguments;
  dlake admin list names them.

• Normal Sync commands need the Admin role. The API key has to belong to a
  user who holds Admin on the tenant. If it doesn't, the command says so plainly
  and exits 3; nothing is changed.

• Adding tables is not the same as syncing them — dlake normalsync readiness
  reports what is still missing, including the parts (the agent install and your
  ERP connection details) that these commands cannot set.

• The bundled Normal Sync guide (dlake skills show dlake-normalsync) and the
  CLI reference ship updated in this version. Upgrade:
  npm install -g @commercient/dlake

0.5.15 (2026-08-19)

• Mainten...

dlake 0.5.24

dlake release notes

0.5.24 (2026-08-26)

• New: Normal Sync resync. dlake normalsync resync --confirm asks the
  on-premises agent to re-pull every synced table on its next run;
  --table <name> queues a single table (SYSPRO custom tables like
  ArCustomer+ are fully supported), and --clear discards the queued list.
  Nothing is deleted or dropped — the agent does the work.
• New: dlake normalsync resync-status. Shows what is queued, plus clone
  coverage: the rows actually present in each clone table against the count
  recorded at the last sync — the quickest way to see whether a sync actually
  moved data, per table.
• The same operations are available to AI agents as four new admin tools, and
  the Normal Sync guide and skills cover them. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.23 (2026-08-26)

• Documentation refresh: the npm package README now describes all eight bundled
  agent skills, including dlake-syncagent.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.22 (2026-08-25)

• Clearer package listing on npm: @commercient/dlake now opens by describing
  what the CLI and the platform actually do, with a first-run example, rather
  than starting with installer internals. Both packages also carry a fuller set
  of keywords, so the CLI is easier to find when searching npm for ERP and CRM
  integration, sync, and SQL Server tooling.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.21 (2026-08-25)

• New agent skill: dlake-syncagent. Installing and configuring the
  Commercient Sync Agent — the Windows agent that runs on your own ERP server and
  actually reads your source data. Covers signing in, listing your licensed
  products, installing one, configuring it per product type, testing the
  connection, and reading the agent's health, using the scriptable
  CommercientSyncAgentCLI.exe. It is the on-premises companion to the existing
  skills, which cover the platform side. Read it with
  dlake skills show dlake-syncagent, or install all of them with
  dlake skills install.
• The Help guide and the CLI reference gained a Sync Agent section covering the
  same ground, including the install-and-test sequence and the exit codes worth
  branching on in a script. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need --confirm, and the command stops before
  doing anything if it is missing. Two of those are worth the extra keystroke:
  the table register is shared by everyone using the same ERP and nothing can
  remove an entry from it, and a row filter is run against your ERP database by
  the on-premises agent exactly as you wrote it.

• The same operations are still available in full. Every verb has a longer
  form as dlake admin normalsync_<name>, with --help for its arguments;
  dlake admin list names them.

• Normal Sync commands need the Admin role. The API key has to belong to a
  user who holds Admin on the tenant. If it doesn't, the command says so plainly
  and exits 3; nothing is changed.

• Adding tables is not the same as syncing them — dlake normalsync readiness
  reports what is still missing, including the parts (the agent install and your
  ERP connection details) that these commands cannot set.

• The bundled Normal Sync guide (dlake skills show dlake-normalsync) and the
  CLI reference ship updated in this version. Upgrade:
  npm install -g @commercient/dlake

0.5.15 (2026-08-19)

• Maintenance: corrected the download-host URL in the bundled guide's install
  example and refreshed package links. No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake)

0.5.14 (2026-08-19)

• Package metadata refresh: the npm package now carries a proper description,
  keywords, and links to the GitHub repository and the official downloads
  site. No functional changes. Upgrade: npm install -g @commercient/dlake

0.5.13 (2026-08-18)

• Updated guidance in the bundled guides and skills. When registering,
  answer one question first: is this an integration (your CRM and/or ERP
  syncing through the platform) or a standalone Data Lake?...

dlake 0.5.23

dlake release notes

0.5.23 (2026-08-26)

• Documentation refresh: the npm package README now describes all eight bundled
  agent skills, including dlake-syncagent.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.22 (2026-08-25)

• Clearer package listing on npm: @commercient/dlake now opens by describing
  what the CLI and the platform actually do, with a first-run example, rather
  than starting with installer internals. Both packages also carry a fuller set
  of keywords, so the CLI is easier to find when searching npm for ERP and CRM
  integration, sync, and SQL Server tooling.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.21 (2026-08-25)

• New agent skill: dlake-syncagent. Installing and configuring the
  Commercient Sync Agent — the Windows agent that runs on your own ERP server and
  actually reads your source data. Covers signing in, listing your licensed
  products, installing one, configuring it per product type, testing the
  connection, and reading the agent's health, using the scriptable
  CommercientSyncAgentCLI.exe. It is the on-premises companion to the existing
  skills, which cover the platform side. Read it with
  dlake skills show dlake-syncagent, or install all of them with
  dlake skills install.
• The Help guide and the CLI reference gained a Sync Agent section covering the
  same ground, including the install-and-test sequence and the exit codes worth
  branching on in a script. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need --confirm, and the command stops before
  doing anything if it is missing. Two of those are worth the extra keystroke:
  the table register is shared by everyone using the same ERP and nothing can
  remove an entry from it, and a row filter is run against your ERP database by
  the on-premises agent exactly as you wrote it.

• The same operations are still available in full. Every verb has a longer
  form as dlake admin normalsync_<name>, with --help for its arguments;
  dlake admin list names them.

• Normal Sync commands need the Admin role. The API key has to belong to a
  user who holds Admin on the tenant. If it doesn't, the command says so plainly
  and exits 3; nothing is changed.

• Adding tables is not the same as syncing them — dlake normalsync readiness
  reports what is still missing, including the parts (the agent install and your
  ERP connection details) that these commands cannot set.

• The bundled Normal Sync guide (dlake skills show dlake-normalsync) and the
  CLI reference ship updated in this version. Upgrade:
  npm install -g @commercient/dlake

0.5.15 (2026-08-19)

• Maintenance: corrected the download-host URL in the bundled guide's install
  example and refreshed package links. No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake)

0.5.14 (2026-08-19)

• Package metadata refresh: the npm package now carries a proper description,
  keywords, and links to the GitHub repository and the official downloads
  site. No functional changes. Upgrade: npm install -g @commercient/dlake

0.5.13 (2026-08-18)

• Updated guidance in the bundled guides and skills. When registering,
  answer one question first: is this an integration (your CRM and/or ERP
  syncing through the platform) or a standalone Data Lake? For an
  integration, pass your real ERP as --instance-type (e.g. SAGEINTACCT)
  so the CRM and connector setup match your ERP from the first step; for a
  standalone Data Lake, omit it — the default is the correct choice there.
  Your Data Lake is created either way.
• The bundled guide now covers the TxDownloaderPro management tools available
  through dlake admin, and the TxDownloaderPro skill gained a section on
  them.
• No behaviour changes. Upgrade: npm install -g @commercient/dlake

0.5.12 (2026-08-18)

• Corrected the wording of the two backup statements on dlake register start.
  --consent-crm-backup and --consent-erp-backup confirm that you have made
  your own backups of your CRM and ERP data — they were previously described
  as consenting to Commercient making backups, which is not what ...

dlake 0.5.22

dlake release notes

0.5.22 (2026-08-25)

• Clearer package listing on npm: @commercient/dlake now opens by describing
  what the CLI and the platform actually do, with a first-run example, rather
  than starting with installer internals. Both packages also carry a fuller set
  of keywords, so the CLI is easier to find when searching npm for ERP and CRM
  integration, sync, and SQL Server tooling.
• No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.21 (2026-08-25)

• New agent skill: dlake-syncagent. Installing and configuring the
  Commercient Sync Agent — the Windows agent that runs on your own ERP server and
  actually reads your source data. Covers signing in, listing your licensed
  products, installing one, configuring it per product type, testing the
  connection, and reading the agent's health, using the scriptable
  CommercientSyncAgentCLI.exe. It is the on-premises companion to the existing
  skills, which cover the platform side. Read it with
  dlake skills show dlake-syncagent, or install all of them with
  dlake skills install.
• The Help guide and the CLI reference gained a Sync Agent section covering the
  same ground, including the install-and-test sequence and the exit codes worth
  branching on in a script. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need --confirm, and the command stops before
  doing anything if it is missing. Two of those are worth the extra keystroke:
  the table register is shared by everyone using the same ERP and nothing can
  remove an entry from it, and a row filter is run against your ERP database by
  the on-premises agent exactly as you wrote it.

• The same operations are still available in full. Every verb has a longer
  form as dlake admin normalsync_<name>, with --help for its arguments;
  dlake admin list names them.

• Normal Sync commands need the Admin role. The API key has to belong to a
  user who holds Admin on the tenant. If it doesn't, the command says so plainly
  and exits 3; nothing is changed.

• Adding tables is not the same as syncing them — dlake normalsync readiness
  reports what is still missing, including the parts (the agent install and your
  ERP connection details) that these commands cannot set.

• The bundled Normal Sync guide (dlake skills show dlake-normalsync) and the
  CLI reference ship updated in this version. Upgrade:
  npm install -g @commercient/dlake

0.5.15 (2026-08-19)

• Maintenance: corrected the download-host URL in the bundled guide's install
  example and refreshed package links. No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake)

0.5.14 (2026-08-19)

• Package metadata refresh: the npm package now carries a proper description,
  keywords, and links to the GitHub repository and the official downloads
  site. No functional changes. Upgrade: npm install -g @commercient/dlake

0.5.13 (2026-08-18)

• Updated guidance in the bundled guides and skills. When registering,
  answer one question first: is this an integration (your CRM and/or ERP
  syncing through the platform) or a standalone Data Lake? For an
  integration, pass your real ERP as --instance-type (e.g. SAGEINTACCT)
  so the CRM and connector setup match your ERP from the first step; for a
  standalone Data Lake, omit it — the default is the correct choice there.
  Your Data Lake is created either way.
• The bundled guide now covers the TxDownloaderPro management tools available
  through dlake admin, and the TxDownloaderPro skill gained a section on
  them.
• No behaviour changes. Upgrade: npm install -g @commercient/dlake

0.5.12 (2026-08-18)

• Corrected the wording of the two backup statements on dlake register start.
  --consent-crm-backup and --consent-erp-backup confirm that you have made
  your own backups of your CRM and ERP data — they were previously described
  as consenting to Commercient making backups, which is not what they mean.
  The flags, their behaviour, and the sign-up flow are unchanged;
  --consent-phone (consent to phone contact) is unchanged. The help text and
  bundled guides now state the correct meaning. Upgrade:
  npm install -g @commercient/dlake

##...

dlake 0.5.21

dlake release notes

0.5.21 (2026-08-25)

• New agent skill: dlake-syncagent. Installing and configuring the
  Commercient Sync Agent — the Windows agent that runs on your own ERP server and
  actually reads your source data. Covers signing in, listing your licensed
  products, installing one, configuring it per product type, testing the
  connection, and reading the agent's health, using the scriptable
  CommercientSyncAgentCLI.exe. It is the on-premises companion to the existing
  skills, which cover the platform side. Read it with
  dlake skills show dlake-syncagent, or install all of them with
  dlake skills install.
• The Help guide and the CLI reference gained a Sync Agent section covering the
  same ground, including the install-and-test sequence and the exit codes worth
  branching on in a script. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need --confirm, and the command stops before
  doing anything if it is missing. Two of those are worth the extra keystroke:
  the table register is shared by everyone using the same ERP and nothing can
  remove an entry from it, and a row filter is run against your ERP database by
  the on-premises agent exactly as you wrote it.

• The same operations are still available in full. Every verb has a longer
  form as dlake admin normalsync_<name>, with --help for its arguments;
  dlake admin list names them.

• Normal Sync commands need the Admin role. The API key has to belong to a
  user who holds Admin on the tenant. If it doesn't, the command says so plainly
  and exits 3; nothing is changed.

• Adding tables is not the same as syncing them — dlake normalsync readiness
  reports what is still missing, including the parts (the agent install and your
  ERP connection details) that these commands cannot set.

• The bundled Normal Sync guide (dlake skills show dlake-normalsync) and the
  CLI reference ship updated in this version. Upgrade:
  npm install -g @commercient/dlake

0.5.15 (2026-08-19)

• Maintenance: corrected the download-host URL in the bundled guide's install
  example and refreshed package links. No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake)

0.5.14 (2026-08-19)

• Package metadata refresh: the npm package now carries a proper description,
  keywords, and links to the GitHub repository and the official downloads
  site. No functional changes. Upgrade: npm install -g @commercient/dlake

0.5.13 (2026-08-18)

• Updated guidance in the bundled guides and skills. When registering,
  answer one question first: is this an integration (your CRM and/or ERP
  syncing through the platform) or a standalone Data Lake? For an
  integration, pass your real ERP as --instance-type (e.g. SAGEINTACCT)
  so the CRM and connector setup match your ERP from the first step; for a
  standalone Data Lake, omit it — the default is the correct choice there.
  Your Data Lake is created either way.
• The bundled guide now covers the TxDownloaderPro management tools available
  through dlake admin, and the TxDownloaderPro skill gained a section on
  them.
• No behaviour changes. Upgrade: npm install -g @commercient/dlake

0.5.12 (2026-08-18)

• Corrected the wording of the two backup statements on dlake register start.
  --consent-crm-backup and --consent-erp-backup confirm that you have made
  your own backups of your CRM and ERP data — they were previously described
  as consenting to Commercient making backups, which is not what they mean.
  The flags, their behaviour, and the sign-up flow are unchanged;
  --consent-phone (consent to phone contact) is unchanged. The help text and
  bundled guides now state the correct meaning. Upgrade:
  npm install -g @commercient/dlake

0.5.11 (2026-08-17)

Please upgrade if you use dlake register — sign-up now requires consent flags.

• Changed: dlake register start requires three affirmation flags.
  Registration now asks for the same three statements as the sign-up website,
  and the server refuses to create an account without them. The backup flags
  confirm that you have made your own backups of your CRM and ERP data
  (they do not ask Commercient to make any backup). Pass each flag to affirm
  i...

dlake 0.5.20

dlake release notes

0.5.20 (2026-08-25)

• New: --generate-password on dlake register start. The CLI can now mint
  the portal password for you: a strong 20-character password that meets the
  portal's password policy, printed once so you can save it. Recommended for
  headless and scripted registrations — the password never touches argv or shell
  history.
• Password checking moved up front. register start now validates the
  password before submitting and, if it refuses, names exactly which characters
  or rules to fix. The portal password is 8–32 characters: letters, digits and
  ! # $ % & * ? @ _ only, with at least one uppercase, one lowercase, one digit
  and one of those specials.
• The Help guide, CLI reference and the registration agent skill were updated to
  match, including the headless registration recipe. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need --confirm, and the command stops before
  doing anything if it is missing. Two of those are worth the extra keystroke:
  the table register is shared by everyone using the same ERP and nothing can
  remove an entry from it, and a row filter is run against your ERP database by
  the on-premises agent exactly as you wrote it.

• The same operations are still available in full. Every verb has a longer
  form as dlake admin normalsync_<name>, with --help for its arguments;
  dlake admin list names them.

• Normal Sync commands need the Admin role. The API key has to belong to a
  user who holds Admin on the tenant. If it doesn't, the command says so plainly
  and exits 3; nothing is changed.

• Adding tables is not the same as syncing them — dlake normalsync readiness
  reports what is still missing, including the parts (the agent install and your
  ERP connection details) that these commands cannot set.

• The bundled Normal Sync guide (dlake skills show dlake-normalsync) and the
  CLI reference ship updated in this version. Upgrade:
  npm install -g @commercient/dlake

0.5.15 (2026-08-19)

• Maintenance: corrected the download-host URL in the bundled guide's install
  example and refreshed package links. No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake)

0.5.14 (2026-08-19)

• Package metadata refresh: the npm package now carries a proper description,
  keywords, and links to the GitHub repository and the official downloads
  site. No functional changes. Upgrade: npm install -g @commercient/dlake

0.5.13 (2026-08-18)

• Updated guidance in the bundled guides and skills. When registering,
  answer one question first: is this an integration (your CRM and/or ERP
  syncing through the platform) or a standalone Data Lake? For an
  integration, pass your real ERP as --instance-type (e.g. SAGEINTACCT)
  so the CRM and connector setup match your ERP from the first step; for a
  standalone Data Lake, omit it — the default is the correct choice there.
  Your Data Lake is created either way.
• The bundled guide now covers the TxDownloaderPro management tools available
  through dlake admin, and the TxDownloaderPro skill gained a section on
  them.
• No behaviour changes. Upgrade: npm install -g @commercient/dlake

0.5.12 (2026-08-18)

• Corrected the wording of the two backup statements on dlake register start.
  --consent-crm-backup and --consent-erp-backup confirm that you have made
  your own backups of your CRM and ERP data — they were previously described
  as consenting to Commercient making backups, which is not what they mean.
  The flags, their behaviour, and the sign-up flow are unchanged;
  --consent-phone (consent to phone contact) is unchanged. The help text and
  bundled guides now state the correct meaning. Upgrade:
  npm install -g @commercient/dlake

0.5.11 (2026-08-17)

Please upgrade if you use dlake register — sign-up now requires consent flags.

• Changed: dlake register start requires three affirmation flags.
  Registration now asks for the same three statements as the sign-up website,
  and the server refuses to create an account without them. The backup flags
  confirm that you have made your own backups of your CRM and ERP data
  (they do not ask Commercient to make any backup). Pass each flag to affirm
  its statement:

  --consent-crm-backup    I confirm I have made my own backup of my CRM data
  --consent-erp-backup    I confirm I have made my own backup of my ERP data
  --consent-phone         I consent to being contacted by phone
  

  Older CLI versions cannot complete register start any more — upgrade:
  npm install -g @commercient/dlake. There is also a new optional
  --document-sync flag for File-Sync-only accounts.

• New: dlake registration oauth — connect an OAuth CRM in one command.
  It opens your browser at the provider's authorization page, catches the
  redirect on this machine, and completes the exchange automatically — no more
  copying code and state out of the address bar. --no-browser keeps the
  manual flow if you prefer it, and the command falls back to it by itself when
  a browser can't be opened.

• **New: `dlake registration act...

dlake 0.5.19

dlake release notes

0.5.19 (2026-08-22)

• Corrected bundled agent-skill guidance. The dlake-apisync skill shipped in
  0.5.18 showed an endpoint-configuration example that could not work: the
  configuration-JSON call omitted the object name, which the platform requires on
  every save. The skill now says so and both examples include it. If you scripted
  from the 0.5.18 example, add --objectName <name> to the JSON call.
• The sync skills now point at each other. dlake-normalsync and
  dlake-integration-setup name dlake-odbcsync (sources that are not
  Microsoft SQL Server) and dlake-apisync (API sources), so an agent working on
  one part of a setup can find the skill for the next part.
• dlake admin apisync_save_endpoint_config now asks for --objectName up front
  and says what is missing, instead of the platform rejecting the call afterwards.
• The CLI reference gained sections for both sync surfaces, and the Help and API
  guides were corrected to match. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

0.5.18 (2026-08-21)

• New: ODBC Sync setup from the CLI. Eight odbcsync_* admin tools configure
  the sync agent for sources that are not Microsoft SQL Server: the S3 bucket
  registry, the bucket's IP allow-list (the step without which the agent cannot
  upload), the agent's configuration file, and two verification reads (what the
  agent has staged, and the last 24 hours of errors).

  dlake admin odbcsync_status
  dlake admin odbcsync_register_bucket --bucketName <name> --confirm true
  dlake admin odbcsync_allow_ip --bucketName <name> --ipAddress <ip> --confirm true
  dlake admin odbcsync_read_agent_config
  

• New: Generic API Sync setup from the CLI. Six apisync_* admin tools turn
  the API-source sync product on and describe the endpoints it calls: enable
  (idempotent), endpoint configurations, the per-ERP endpoint-template catalogue,
  and a hosted customer's real ERP table columns.

  dlake admin apisync_status
  dlake admin apisync_enable --confirm true
  dlake admin apisync_templates --erpName <erp>
  

• Every new tool is Admin-only (reads included), acts only on the key's own
  tenant, and shows its argument schema with dlake admin <tool> --help.

• Two new bundled agent skills — dlake-odbcsync and dlake-apisync —
  teach an AI agent both surfaces, including the ordering and the traps (the
  config editor's encrypted settings; the endpoint save's two modes).

• The Help and API guides gain matching sections. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake).

• If your MCP client was already connected, restart it (or re-add the connector)
  to see the new tools — the tool list is cached per session.

0.5.17 (2026-08-21)

• Updated bundled agent skills. The integration-setup skill now gives an AI
  agent much firmer guidance through the CRM OAuth step:
  • which callback style to use per CRM (HubSpot always uses the website
    flow - no local listener needed, and the browser can be on any machine);
  • completing the token exchange promptly once the authorization lands
    (authorization codes are short-lived);
  • that confirmation PINs arrive by email after the exchange completes -
    they are never shown on screen;
  • asking you before deferring a CRM connection or submitting placeholder ERP
    credentials, and saying clearly when a setup will not sync yet.
• The npm packages (@commercient/dlake and the datalake alias) now link
  the GitHub repository and the browsable skills folder from their pages.
• No CLI command changes. Upgrade: npm install -g @commercient/dlake
  (or npm install -g datalake).

0.5.16 (2026-08-19)

• New: dlake normalsync — choose which of your ERP tables get synced, from the
  command line. Normal Sync is the on-premises agent that copies changed rows
  out of your ERP database and into your Data Lake; this group is the table
  selection for it:

  dlake normalsync tables                 tables you could add
  dlake normalsync selected               tables you have added, and their settings
  dlake normalsync readiness              is the sync actually set up, and if not why
  dlake normalsync select <table> <id>    add a table to your sync
  dlake normalsync enable | disable <table> <id>   turn one table's sync on or off
  dlake normalsync filter <id> --where "<sql>" --confirm   sync only some rows
  dlake normalsync filter <id> --clear --confirm          sync the whole table again
  dlake normalsync catalog <table> --confirm   register a table name for your ERP
  dlake normalsync add <table> --confirm      register it and add it in one step
  

  catalog, add and filter need --confirm, and the command stops before
  doing anything if it is missing. Two of those are worth the extra keystroke:
  the table register is shared by everyone using the same ERP and nothing can
  remove an entry from it, and a row filter is run against your ERP database by
  the on-premises agent exactly as you wrote it.

• The same operations are still available in full. Every verb has a longer
  form as dlake admin normalsync_<name>, with --help for its arguments;
  dlake admin list names them.

• Normal Sync commands need the Admin role. The API key has to belong to a
  user who holds Admin on the tenant. If it doesn't, the command says so plainly
  and exits 3; nothing is changed.

• Adding tables is not the same as syncing them — dlake normalsync readiness
  reports what is still missing, including the parts (the agent install and your
  ERP connection details) that these commands cannot set.

• The bundled Normal Sync guide (dlake skills show dlake-normalsync) and the
  CLI reference ship updated in this version. Upgrade:
  npm install -g @commercient/dlake

0.5.15 (2026-08-19)

• Maintenance: corrected the download-host URL in the bundled guide's install
  example and refreshed package links. No functional changes. Upgrade:
  npm install -g @commercient/dlake (or npm install -g datalake)

0.5.14 (2026-08-19)

• Package metadata refresh: the npm package now carries a proper description,
  keywords, and links to the GitHub repository and the official downloads
  site. No functional changes. Upgrade: npm install -g @commercient/dlake

0.5.13 (2026-08-18)

• Updated guidance in the bundled guides and skills. When registering,
  answer one question first: is this an integration (your CRM and/or ERP
  syncing through the platform) or a standalone Data Lake? For an
  integration, pass your real ERP as --instance-type (e.g. SAGEINTACCT)
  so the CRM and connector setup match your ERP from the first step; for a
  standalone Data Lake, omit it — the default is the correct choice there.
  Your Data Lake is created either way.
• The bundled guide now covers the TxDownloaderPro management tools available
  through dlake admin, and the TxDownloaderPro skill gained a section on
  them.
• No behaviour changes. Upgrade: npm install -g @commercient/dlake

0.5.12 (2026-08-18)

• Corrected the wording of the two backup statements on dlake register start.
  --consent-crm-backup and --consent-erp-backup confirm that you have made
  your own backups of your CRM and ERP data — they were previously described
  as consenting to Commercient making backups, which is not what they mean.
  The flags, their behaviour, and the sign-up flow are unchanged;
  --consent-phone (consent to phone contact) is unchanged. The help text and
  bundled guides now state the correct meaning. Upgrade:
  npm install -g @commercient/dlake

0.5.11 (2026-08-17)

Please upgrade if you use dlake register — sign-up now requires consent flags.

• Changed: dlake register start requires three affirmation flags.
  Registration now asks for the same three statements as the sign-up website,
  and the server refuses to create an account without them. The backup flags
  confirm that you have made your own backups of your CRM and ERP data
  (they do not ask Commercient to make any backup). Pass each flag to affirm
  its statement:

  --consent-crm-backup    I confirm I have made my own backup of my CRM data
  --consent-erp-backup    I confirm I have made my own backup of my ERP data
  --consent-phone         I consent to being contacted by phone
  

  Older CLI versions cannot complete register start any more — upgrade:
  npm install -g @commercient/dlake. There is also a new optional
  --document-sync flag for File-Sync-only accounts.

• New: dlake registration oauth — connect an OAuth CRM in one command.
  It opens your browser at the provider's authorization page, catches the
  redirect on this machine, and completes the exchange automatically — no more
  copying code and state out of the address bar. --no-browser keeps the
  manual flow if you prefer it, and the command falls back to it by itself when
  a browser can't be opened.

• New: dlake registration action — the provider-specific setup steps.
  Salesforce's managed-package install links and Monday's workspace picker
  (SalesforceSetup, MondayListWorkspaces, MondayPickWorkspace) are now
  reachable from the CLI; previously these steps could not be completed outside
  the portal.

• The bundled guides and the integration-setup skill are updated to match.

0.5.10 (2026-08-15)

• Refreshed the built-in guides and documentation. No functional changes.
• Downloads for older versions have been retired; installs of pinned versions
  below 0.5.10 will no longer fetch binaries. Upgrade:
  npm install -g @commercient/dlake

0.5.9 (2026-08-15)

• New: dlake crmpro — run CRMPro from the command line. The everyday verbs
  for the forward ERP→CRM sync, without opening the portal:

  dlake crmpro processes [--active]     the sync grid
  dlake crmpro process <id>             one proce...