You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 20934c1
Browse filesBrowse the repository at this point in the historyBrowse files
Merge branch 'development' into fix/snyk-issues-24-06-26
Brings in the 27 commits development gained after the previous merge
(PR #217 Asset-Scanning-v1, #322, #323 and others), clearing the conflict
that was blocking PR #243 and preventing GitHub Actions from producing a
merge ref.
Only .talismanrc conflicted. Resolved to the checksum for the merged
pnpm-lock.yaml (95ad8483..., confirmed via `talisman --checksum`) and moved
`version` back to the top level, where talisman expects it — development's
side had it indented under the fileignoreconfig entry.
Verified before push:
- `pnpm install --frozen-lockfile` passes (the auto-merged lockfile is
self-consistent; this is the check that caught the broken lockfile in
PR #324 and the dropped `open` dependency in the previous merge)
- dependency sweep against both merge parents: nothing lost
- undeclared-import sweep unchanged from baseline: no new hybrids
- test suites for all six packages this merge touched:
contentstack-audit 160 passing
contentstack-export 485 passing
contentstack-external-migrate 42 passing
contentstack-import 1736 passing
contentstack-query-export 139 passing
contentstack-bulk-publish (no test script)
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments