Skip to content

Conversation

@joshwlewis
Copy link
Collaborator

@joshwlewis joshwlewis commented Apr 12, 2022

What does this PR do?

Updates @salesforce/functions-core to 0.2.8. Which includes some function template updates: https://github.com/heroku/sf-functions-core/pull/46 and https://github.com/heroku/sf-functions-core/pull/43.

What issues does this PR fix or reference?

@W-10728914@

@uip-robot-zz
Copy link

Git2Gus App is installed but the .git2gus/config.json doesn't exist.

@joshwlewis joshwlewis requested a review from mimen April 12, 2022 16:36
@joshwlewis joshwlewis changed the title fix: bump functions-core to 0.2.8 fix: update functions templates with functions-core to 0.2.8 Apr 12, 2022
@joshwlewis joshwlewis changed the title fix: update functions templates with functions-core to 0.2.8 fix: update functions templates with functions-core 0.2.8 Apr 12, 2022
@joshwlewis joshwlewis merged commit a5f6428 into main Apr 13, 2022
@joshwlewis joshwlewis deleted the function-core-0.2.8 branch April 13, 2022 20:00
colincasey added a commit that referenced this pull request Apr 18, 2022
* main:
  fix: update functions templates with functions-core 0.2.8 (#403)

# Conflicts:
#	package.json
#	test/commands/run/function/start.test.ts
#	yarn.lock
@edmorley
Copy link
Member

@joshwlewis Hi! Why was the @heroku/functions-core package path aliased to @hk/functions-core in this PR?

The commit message gives no reason other than:
chore: shorten @heroku/functions-core path

The shortened path is harder to grep when doing eg GitHub code search, and is inconsistent with all other packages in this project and how people typically use package.json, so my preference would be to revert this change unless there is a technical need for it?

@joshwlewis
Copy link
Collaborator Author

The commit previous to that failed CI: https://circleci.com/gh/salesforcecli/plugin-functions/8514?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link. There's a check that ensures no file paths are beyond a certain length to prevent compatibility issues on Windows. ¯_(ツ)_/¯

@joshwlewis
Copy link
Collaborator Author

@edmorley - Here's a related PR in which I shortened the paths in sf-functions-core for the same reason: https://github.com/heroku/sf-functions-core/pull/22

edmorley added a commit that referenced this pull request Jan 31, 2023
In #403 and heroku/sf-functions-core#22 various
measures were taken to try and shorten the maximum on-disk filepath of files
in the two packages, so as to prevent the CI failures seen in:
https://app.circleci.com/pipelines/github/salesforcecli/plugin-functions/2415/workflows/510a1bac-1a64-4a1b-a5a5-e765100b08d2/jobs/8514

One of these measure was to use a package alias of `@hk/functions-core` for the
`@heroku/functions-core` package, so the on-disk directory path was 4 characters
shorter.

However, this change stops Dependabot from working, and looking at recent tarfile
verification logs in CI, it appears we might not need to save these four characters any
more - since none of the salesforce-core dep paths appear in the "close to the limit"
warnings.

As such, we can undo this aliasing, to fix Dependabot for this package.
edmorley added a commit that referenced this pull request Jan 31, 2023
…ency name

In #403 and heroku/sf-functions-core#22 various
measures were taken to try and shorten the maximum on-disk filepath of files
in the two packages, so as to prevent the CI failures seen in:
https://app.circleci.com/pipelines/github/salesforcecli/plugin-functions/2415/workflows/510a1bac-1a64-4a1b-a5a5-e765100b08d2/jobs/8514

One of these measure was to use a package alias of `@hk/functions-core` for the
`@heroku/functions-core` package, so the on-disk directory path was 4 characters
shorter.

However, this change stops Dependabot from working, and looking at recent tarfile
verification logs in CI, it appears we might not need to save these four characters any
more - since none of the salesforce-core dep paths appear in the "close to the limit"
warnings.

As such, we can undo this aliasing, to fix Dependabot for this package.
edmorley added a commit that referenced this pull request Jan 31, 2023
…ency name

In #403 and heroku/sf-functions-core#22 various
measures were taken to try and shorten the maximum on-disk filepath of files
in the two packages, so as to prevent the CI failures seen in:
https://app.circleci.com/pipelines/github/salesforcecli/plugin-functions/2415/workflows/510a1bac-1a64-4a1b-a5a5-e765100b08d2/jobs/8514

One of these measure was to use a package alias of `@hk/functions-core` for the
`@heroku/functions-core` package, so the on-disk directory path was 4 characters
shorter.

However, this change stops Dependabot from working, and looking at recent tarfile
verification logs in CI, it appears we might not need to save these four characters any
more - since none of the salesforce-core dep paths appear in the "close to the limit"
warnings.

As such, we can undo this aliasing, to fix Dependabot for this package.

@W-12466399@
edmorley added a commit that referenced this pull request Feb 1, 2023
…ency name (#595)

In #403 and heroku/sf-functions-core#22 various
measures were taken to try and shorten the maximum on-disk filepath of files
in the two packages, so as to prevent the CI failures seen in:
https://app.circleci.com/pipelines/github/salesforcecli/plugin-functions/2415/workflows/510a1bac-1a64-4a1b-a5a5-e765100b08d2/jobs/8514

One of these measure was to use a package alias of `@hk/functions-core` for the
`@heroku/functions-core` package, so the on-disk directory path was 4 characters
shorter.

However, this change stops Dependabot from working, and looking at recent tarfile
verification logs in CI, it appears we might not need to save these four characters any
more - since none of the salesforce-core dep paths appear in the "close to the limit"
warnings.

As such, we can undo this aliasing, to fix Dependabot for this package.

@W-12466399@
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants