Skip to content

Configure Renovate#13

Merged
jancurn merged 1 commit intomainfrom
renovate/configure
Mar 2, 2026
Merged

Configure Renovate#13
jancurn merged 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 1, 2026 •
edited
Loading

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

  • .github/workflows/ci.yml (github-actions)
  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

What to Expect

With your current configuration, Renovate will create 5 Pull Requests:

chore(deps): update dependency @​types/node to v25.3.3
  • Schedule: ["at any time"]
  • Branch name: renovate/node-25.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 25.3.3
chore(deps): update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update actions/setup-node action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update dependency eslint to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade eslint to ^10.0.0
chore(deps): update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR was generated by Mend Renovate. View the repository job log.

@jancurn jancurn merged commit 3861f51 into main Mar 2, 2026
4 of 5 checks passed
@renovate renovate Bot deleted the renovate/configure branch March 2, 2026 10:21
MQ37 added a commit that referenced this pull request Mar 3, 2026
@MQ37
Squashed commit of the following:
9072970 
commit 1e35f2f
Author: Dušan Vystrčil <vystrcil.dusan@gmail.com>
Date:   Tue Mar 3 10:25:50 2026 +0100

    fix: flush stdout before process.exit() to prevent pipe truncation (#17)

    When mcpc output exceeds 64KB and stdout is piped (e.g. `mcpc ... --json | jq`),
    the output was silently truncated at exactly 65,536 bytes (the kernel pipe buffer
    size), producing broken JSON.

    Root cause: when stdout is a pipe, Node.js uses async I/O. `process.exit(0)`
    terminates the process before buffered data is fully written to the pipe. When
    stdout is a file or TTY, Node.js uses sync I/O, so data is written before exit.

    The fix waits for stdout to drain before calling process.exit(0).

    Reproduction:
      mcpc @apify tools-call get-actor-output datasetId:="..." --json | wc -c

    Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

commit c7ea6f2
Author: Jan Curn <jan.curn@gmail.com>
Date:   Mon Mar 2 13:15:22 2026 +0100

    Updated CHANGELOG.md, improved release process

commit 3861f51
Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Date:   Mon Mar 2 11:19:49 2026 +0100

    Add renovate.json (#13)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

commit ba193b8
Author: Jan Curn <jan.curn@gmail.com>
Date:   Sun Mar 1 23:36:16 2026 +0100

    v0.1.10

commit 8400ca3
Author: Jan Curn <jan.curn@gmail.com>
Date:   Sun Mar 1 23:21:57 2026 +0100

    Added support for `HTTPS_PROXY` / `HTTP_PROXY` / `NO_PROXY` env vars (#10)

    * Added support for `HTTPS_PROXY` / `https_proxy` / `HTTP_PROXY` / `http_proxy` env vars

    * Improvements

    * Improvements

    * Fixes

    * Fixes

    * Nits
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jancurn @apify-service-account