-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build started failing #11057
Comments
Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned. |
@frontendphil Thanks for reporting. The error is shown when there are some placeholders in the |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate. |
Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible. |
Describe the bug
Our builds started failing when the new version
@microsoft/teamsapp-cli
was published. We're seeing this error, when runningteamsapp pakcage
.To Reproduce
Steps to reproduce the behavior:
teamsapp package
Expected behavior
The
env
input should not be mandatory (at least not according to the docs)Screenshots
See above
VS Code Extension Information (please complete the following information):
node:21.6.2-alpine3.18
)Additional context
Builds started failing in the last hour. We're always using the latest version of this package in our pipeline.
The text was updated successfully, but these errors were encountered: