Yeikel Santana
Yeikel Santana
As part of this recipe, we should make the wrapper executable: ```shell chmod +x mvnw ``` Otherwise, some CI environments (like GH actions), will throw this: `./mvnw: Permission denied` We...
This turned out to be quite complicated to implement. And I don't think we need it as it happens very rarely Feel to re-open it if needed
If you decide to use Semantic commits [the semantic pull request validation action](https://github.com/amannn/action-semantic-pull-request) is very useful In my team, we use a combination of semantic + squash workflow (discussed in...
What is the status of this change and what prevent it from moving forward? The issue (if still exists) is concerning
@sp-gupta Would you be able to comment here? Or at least get someone who could? Thanks!
Did this ever get resolved? I am also seeing this one along with #739 and I am using the latest version of the connector
@deivid-rodriguez What do you think about this change? We're still pinning the npm and yarn versions so it should be fine?
> Currently we run a fixed version on nodejs, so that means we are not able to support applications with certain nodejs constraints. For example, if someone specifying "node": "^18.12.0"...
@deivid-rodriguez What changed that you decided to approve it? I am just curious as your points were valid and interesting Thank you!
@abdulapopoola @jakecoffman Could you please help me to assign a point of contact now that Deivid lost the necessary access to check the metrics (or that's what I understand) ?