Skip to content

Commit 2070190

Browse files
committed
Merge branch 'master' into biz/dj-2678-make-environment-mandatory-in-connect-sdk
2 parents d0362d0 + 9cbf1c2 commit 2070190

File tree

2 files changed

+19
-0
lines changed

2 files changed

+19
-0
lines changed

docs-v2/pages/projects/git.mdx

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -198,6 +198,21 @@ Yes, you can use the GitHub Syncing feature to develop your workflows from YAML
198198

199199
Then pushing changes to the `production` branch will trigger a deploy for your Pipedream workflows.
200200

201+
### Why am I seeing the error "could not resolve step[index].uses: component-key@version" when merging to production?
202+
This error occurs when a workflow references a [private component](https://pipedream.com/docs/components#using-private-actions) without properly prefixing the component key with your workspace name in the `workflow.yaml` configuration file. Pipedream requires this prefix to correctly identify and resolve components specific to your workspace.
203+
204+
For example, if you modified a [registry action](https://pipedream.com/docs/apps/contributing) and published it privately, the correct component key should be formatted as `@workspacename/component-key@version` (e.g., `@pipedream/[email protected]`).
205+
206+
To resolve this error:
207+
208+
1. Clone your repository locally and create a development branch.
209+
2. Locate the error in your `workflow.yaml` file where the component key is specified.
210+
3. Add your workspace name prefix to the component key, ensuring it follows the format `@workspacename/component-key@version`.
211+
4. Commit your changes and push them to your repository.
212+
5. Open your project in the Pipedream UI and select your development branch.
213+
6. Click on **Merge to Production** and verify the deployment success in the [Changelog](https://pipedream.com/docs/projects/git#use-the-changelog).
214+
7. If the issue persists, [reach out to Pipedream Support](https://pipedream.com/support) for further assistance.
215+
201216
### Why am I seeing an error about "private auth mismatch" when trying to merge a branch to production?
202217
![Private Auth Mismatch](https://res.cloudinary.com/pipedreamin/image/upload/v1704258143/private_auth_mismatch_kzdd7e.png)
203218

docs-v2/pages/troubleshooting.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,10 @@ If you're encountering a specific issue in a workflow, try the following steps,
3030

3131
If you're still seeing the issue after trying these steps, please reach out in [the community](https://pipedream.com/support).
3232

33+
## I need help with my GitHub Synced Project
34+
35+
[See FAQ here](https://pipedream.com/docs/projects/git#frequently-asked-questions).
36+
3337
## Why is my trigger not emitting events?
3438

3539
Most Pipedream sources fall into one of two categories: webhook-based or timer-based.

0 commit comments

Comments
 (0)