@saidsef/tracing-node 1.8.12 → 1.8.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CONTRIBUTING.md +65 -0
  2. package/package.json +3 -3
package/CONTRIBUTING.md ADDED
@@ -0,0 +1,65 @@
1
+ # Contributing
2
+
3
+ When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
4
+
5
+ Please note we have a code of conduct, please follow it in all your interactions with the project.
6
+
7
+ ## Pull Request Process
8
+
9
+ 1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
10
+ 2. Update the `package.json`, run `npm run rebuild` and add commit message with details of changes, this includes new environment variables, useful file locations and parameters.
11
+ 3. Increase the version numbers is managed by the GitHub Actions CI workflow via `tagging.yml` and `release.yml`
12
+ 4. You may merge the Pull Request in once you have the sign-off of from the project team, or if you do not have permission to do that, you may request a reviewer to merge it for you.
13
+
14
+ ## Code of Conduct
15
+
16
+ ### Our Pledge
17
+
18
+ In the interest of fostering an open and welcoming environment, we as
19
+ contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
20
+
21
+ ### Our Standards
22
+
23
+ Examples of behavior that contributes to creating a positive environment include:
24
+
25
+ * Using welcoming and inclusive language
26
+ * Being respectful of differing viewpoints and experiences
27
+ * Gracefully accepting constructive criticism
28
+ * Focusing on what is best for the community
29
+ * Showing empathy towards other community members
30
+
31
+ Examples of unacceptable behavior by participants include:
32
+
33
+ * The use of sexualized language or imagery and unwelcome sexual attention or
34
+ advances
35
+ * Trolling, insulting/derogatory comments, and personal or political attacks
36
+ * Public or private harassment
37
+ * Publishing others' private information, such as a physical or electronic
38
+ address, without explicit permission
39
+ * Other conduct which could reasonably be considered inappropriate in a
40
+ professional setting
41
+
42
+ ### Our Responsibilities
43
+
44
+ Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
45
+
46
+ Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
47
+
48
+ ### Scope
49
+
50
+ This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
51
+
52
+ ### Enforcement
53
+
54
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
55
+
56
+ Further details of specific enforcement policies may be posted separately.
57
+
58
+ Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
59
+
60
+ ### Attribution
61
+
62
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
63
+
64
+ [homepage]: http://contributor-covenant.org
65
+ [version]: http://contributor-covenant.org/version/1/4/
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@saidsef/tracing-node",
3
- "version": "1.8.12",
3
+ "version": "1.8.13",
4
4
  "description": "tracing NodeJS - This is a wrapper for OpenTelemetry instrumentation packages",
5
5
  "main": "libs/index.js",
6
6
  "scripts": {
@@ -35,12 +35,12 @@
35
35
  "homepage": "https://github.com/saidsef/tracing-nodejs#readme",
36
36
  "dependencies": {
37
37
  "@opentelemetry/api": "^1.6.0",
38
- "@opentelemetry/exporter-trace-otlp-grpc": "^0.43.0",
38
+ "@opentelemetry/exporter-trace-otlp-grpc": "^0.44.0",
39
39
  "@opentelemetry/instrumentation": "^0.44.0",
40
40
  "@opentelemetry/instrumentation-aws-sdk": "^0.36.0",
41
41
  "@opentelemetry/instrumentation-dns": "^0.32.2",
42
42
  "@opentelemetry/instrumentation-express": "^0.33.1",
43
- "@opentelemetry/instrumentation-http": "^0.43.0",
43
+ "@opentelemetry/instrumentation-http": "^0.44.0",
44
44
  "@opentelemetry/instrumentation-pino": "^0.34.1",
45
45
  "@opentelemetry/propagator-b3": "^1.17.0",
46
46
  "@opentelemetry/resources": "^1.17.0",