denis256 notes and projects

ingestr v1.0.66 was published on July 6, 2026, as a small stable release for OneLake path handling. The important change is that OneLake now skips Fabric managed area directories, which should make table path discovery less noisy for jobs pointed at Fabric controlled storage areas. It is not marked as a prerelease.

The full release notes and downloads are on the GitHub release page.

OneLake skips Fabric managed directories

The functional changelog entry in v1.0.66 is onelake: skip fabric-managed area directories. That is a tight change, but it sits in an awkward part of data tooling: path discovery. When a connector is working out which table paths belong to a run, implementation directories can look like real work unless the code knows to ignore them.

For OneLake users, the practical result should be cleaner table path handling. ingestr should leave Fabric managed areas out of the path set instead of treating them as candidates for pipeline work. The release notes do not claim a new destination, a new source, or a new command. They point at a small correction in how the existing OneLake code decides what to walk.

Why operators should care

This release matters most for teams that run ingestr against OneLake locations where system owned directories sit near table data. Those directories are part of the storage environment, but they are not usually the data an ingestion job is trying to move. Including them in discovery creates noise at best and confusing run behavior at worst.

The nice part is that the change should be easy to reason about during rollout. If a pipeline already reads normal table paths, the expected result after v1.0.66 is that those paths still appear. The paths that Fabric manages for its own area should drop out of ingestr’s consideration. That is not flashy, but it is the kind of fix that reduces sharp edges for people on call.

A deliberately narrow changelog

The other listed entry is the merge of pull request #924 from bruin-data/onelake-table-path-2. The release notes do not describe any wider behavior change beyond the OneLake table path work. That matters because ingestr has had recent releases with broader connector additions and schema work; this tag is much smaller.

That small scope is useful information. Operators can review it as a targeted OneLake patch rather than a release that changes several connectors at once. There is no note about breaking changes, deprecated settings, data format changes, or migration work. If your environment does not use OneLake, the release notes do not show an obvious user facing change for you.

What to check after upgrade

For OneLake users, the main check is path selection. Run a representative job against a location that includes Fabric managed directories and confirm that only the intended table paths are considered. Keep the validation boring: table data should remain in scope, and Fabric managed areas should stay out of the run.

No new CLI flags or config keys are named in the notes. There is also no prerelease marker in release.json, so v1.0.66 should be treated as a normal release by release automation. The safe reading is simple: upgrade for the OneLake directory skip, then watch the first runs that depend on OneLake path discovery.

Where to get it

• Release page: GitHub release page
• Repository: project repo
• Tag: v1.0.66