Skip to content

ci(deps): Bump actions/checkout from 4 to 7#5

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-6
Closed

ci(deps): Bump actions/checkout from 4 to 7#5
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 15, 2026

Copy link
Copy Markdown

Bumps actions/checkout from 4 to 7.

Release notes

Sourced from actions/checkout's releases.

v7.0.0

What's Changed

New Contributors

Full Changelog: actions/checkout@v6.0.3...v7.0.0

v6.0.3

What's Changed

New Contributors

Full Changelog: actions/checkout@v6...v6.0.3

v6.0.2

What's Changed

Full Changelog: actions/checkout@v6.0.1...v6.0.2

v6.0.1

What's Changed

Full Changelog: actions/checkout@v6...v6.0.1

v6.0.0

What's Changed

... (truncated)

Changelog

Sourced from actions/checkout's changelog.

Changelog

v7.0.0

v6.0.3

v6.0.2

v6.0.1

v6.0.0

v5.0.1

v5.0.0

v4.3.1

v4.3.0

v4.2.2

v4.2.1

... (truncated)

Commits

@dependabot @github

dependabot Bot commented on behalf of github Jun 15, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot changed the title ci(deps): Bump actions/checkout from 4 to 6 ci(deps): Bump actions/checkout from 4 to 7 Jun 29, 2026
@dependabot dependabot Bot force-pushed the dependabot/github_actions/actions/checkout-6 branch from 29a5a4a to ed045ae Compare June 29, 2026 22:39
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 7.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4...v7)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/github_actions/actions/checkout-6 branch from ed045ae to de1df12 Compare June 30, 2026 17:26
@dependabot @github

dependabot Bot commented on behalf of github Jul 1, 2026

Copy link
Copy Markdown
Author

Superseded by #8.

@dependabot dependabot Bot closed this Jul 1, 2026
@dependabot dependabot Bot deleted the dependabot/github_actions/actions/checkout-6 branch July 1, 2026 23:27
exbuf added a commit that referenced this pull request Jul 2, 2026
adopters see themselves first; drop artificial "Home user"
identity segregation

The list opened with **Home user** (least likely PyPI/GitHub
discoverer) and buried the technical roles most likely to reach
peekdocs through Python-packaging channels at positions #10–12
(AI/ML engineer, Engineer, Developer / programmer). A first-time
visitor arriving from a GitHub search for "python document
search cli" scrolled past four non-technical bullets before
seeing themselves.

Also, having **Home user** as one bullet among "Office worker /
Developer / Sysadmin" implicitly framed the other 12 bullets as
NOT home users — contradicting the "entirely on your own
computer" opening. peekdocs is local-only; every user IS a
home user.

**Reordered** so tech-heavy adopters land at the top:

  1. Developer / programmer     (was #12)
  2. Sysadmin                   (was #6)
  3. AI/ML engineer             (was #10)
  4. IT consultant              (was #4, expanded)
  5. Data researcher            (was #9)
  6. Engineer                   (was #11)
  7. Documentation team         (was #7)
  8. Auditor or review          (was #5)
  9. Researcher                 (was #8)
  10. Small business owner      (was #3, absorbed the Home-user
                                 tax-search scenario as a
                                 "Personal side" note)
  11. Office worker             (was #2)

**Dropped two bullets:**

  - **Home user** — the "everybody is a home user" framing now
    lives in the section's opening paragraph ("entirely on your
    own computer"), applying to every bullet rather than being
    one bullet's identity. The tax-search scenario is folded
    into Small business owner as a "Personal side" note so no
    concrete example is lost.

  - **Email archives** — was a file type, not a role. Odd one
    out in a role-shaped list. Already covered by the intro's
    file-type enumeration (Word, PDF, Excel, email, scanned
    documents, archives, and 100+ more).

**Enhanced two one-liners:**

  - **Sysadmin** was "Search 20 GB of log files for a request ID
    across mixed archives." Added the `.gz`/`.bz2`/`.zip`/`.tar`
    detail (read natively without unpacking) and the --watch
    NDJSON streaming detail for pipeline integration.

  - **IT consultant** was "Search a folder of client documents
    for a set of terms." Added the standalone-binary-on-USB
    workflow (--output-dir back to the USB, --no-index for zero
    artifacts) and a cross-link to the Portable / consulting
    use section added earlier this session (fc9fd98).

All other bullets keep their descriptions verbatim — only their
position in the list changed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
exbuf added a commit that referenced this pull request Jul 2, 2026
"Preparing the USB — one-time setup" walkthrough + two new
gotchas (Windows Group Policy, Tesseract not bundled)

The prior "Setup — done once" paragraph was a one-liner —
"grab the binaries and drop them onto the USB." Too thin for
consultants first attempting the workflow, and left several
practical questions unanswered:

  - Which binaries + what sizes?
  - Do I need Python on the USB too?  (No — the standalone
    binaries ARE Python + deps + peekdocs; this is now stated
    explicitly to head off the question.)
  - How do I verify what I downloaded is what shipped?
  - What USB folder structure is sane?
  - Should I unzip .app bundles now or at the client?
  - What do I do BEFORE the engagement to catch issues?

**Section retitled and expanded — "Preparing the USB — one-time
setup":**

  - Opens with "You do not carry Python on the USB and you do
    not install Python on the client machine." — direct answer
    to the recurring "do I also need a portable-Python
    distribution?" question, before it gets asked.
  - Six-binary + checksums-file listing with per-file sizes
    (78 MB Windows CLI, 103 MB macOS CLI zip, 114 MB Linux
    CLI, 78 MB Windows GUI, 200 MB macOS GUI zip, 114 MB
    Linux GUI, 530 B SHA256SUMS).
  - CLI-vs-GUI decision guidance (preserved from prior edit).
  - SHA-256 verification step — one-liner for macOS/Linux
    (shasum -a 256 -c peekdocs_SHA256SUMS.txt), PowerShell
    equivalent for Windows (Get-FileHash + manual compare).
  - macOS .app pre-unzip guidance with the ExFAT-doesn't-
    preserve-xattrs rationale for why quarantine flag often
    doesn't survive the copy.
  - Recommended USB folder structure (windows/ macos/ linux/
    subdirs + checksums + peekdocs_reports/ output target +
    scripts/ wrapper directory).
  - --check verification step (preserved from prior edit).
  - Rehearsal step — "run the actual command on a scratch
    folder matching the client's OS before you're on the
    clock." Catches paths-with-spaces and aggressive-SmartScreen
    surprises early.

**"Four gotchas" → "Six gotchas" — new #5 and #6:**

  - **#5 Corporate Windows execution restrictions.** Group
    Policy and Windows Defender Controlled Folder Access can
    block .exe launches from removable drives. Verify with
    client IT before assuming the workflow works; fallback
    options named (temporary whitelist / pipx-install on
    client / launch from a Group-Policy-permitted directory).

  - **#6 Tesseract for OCR is NOT bundled.** The standalone
    binaries carry Python + Python dependencies only. If OCR
    of scanned PDFs or image files is in scope: install
    Tesseract on the client (footprint, may need admin),
    pre-OCR docs on own machine before the engagement (produce
    searchable copies), or scope OCR out. Cross-links
    peekdocs --check as the on-site diagnostic that reports
    Tesseract's presence.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
exbuf added a commit that referenced this pull request Jul 2, 2026
Docs-only bump for the Portable / consulting use section
expansions in 788487c (GUI variants coverage in Gotcha 4) and
6b3b57c (Preparing the USB one-time setup walkthrough + new
gotchas #5 Windows Group Policy and #6 Tesseract not bundled).
No code changes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants