Consistently update segmentTimeoutInMs everywhere

Open Beginner friendly
#1,416 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

Start by comparing packages/cache/src/options.ts and packages/cache/src/internal/downloadUtils.ts with the new segmentTimeoutInMs default, then check packages/cache/RELEASES.md around the referenced entry. Update the listed code and release documentation so they consistently reflect the new default, and verify the cache package tests or checks pass.

Written by the indexing model from the issue text.

Description

These were not updated to match the new default:

and README was updated in https://github.com/actions/toolkit/pull/1367 but RELEASES wasn't https://github.com/actions/toolkit/blob/457303960f03375db6f033e214b9f90d79c3fe5c/packages/cache/RELEASES.md?plain=1#L160-L162

Originally posted by @lukaw3d in https://github.com/actions/toolkit/pull/1363#discussion_r1170677923

Dominant language
TypeScript
Stars
5.9k
Forks
1.8k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/toolkit

All issues in actions/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.