|
51 | 51 | - `src/EventListener/TracingRequestListener.php` temporarily injects the active |
52 | 52 | request into `RequestFetcher` and clears it on terminate. Keep that set/reset |
53 | 53 | lifecycle balanced if you change request tracing. |
| 54 | +- `SentryBundle::SDK_VERSION` is updated by the release action. Do not modify |
| 55 | + it manually as part of normal development changes. |
54 | 56 | - `BufferFlushPass`, logging, and metrics code are sensitive to terminate-time |
55 | 57 | behavior. Add end-to-end coverage when changing those paths. |
56 | 58 |
|
|
70 | 72 | - `README.md` and `CHANGELOG.md` are updated manually during releases, so do |
71 | 73 | not modify them as part of normal development changes. |
72 | 74 | - If a change may require updates in the separate documentation repo, ask the |
73 | | - user whether to review their locally checked out docs. The user must provide |
74 | | - the local path. If they opt in, update that repo's `master` branch when safe, |
75 | | - use git worktrees to inspect the relevant docs, and suggest any needed |
76 | | - changes to avoid stale documentation. |
77 | | -- Add or update an `UPGRADE-*.md` file when a change is breaking or alters the |
78 | | - upgrade path. |
| 75 | + user whether to review `../sentry-docs` if that sibling checkout exists. If |
| 76 | + it does not exist, ask the user for the local docs path first. If they opt |
| 77 | + in, update that repo's `master` branch when safe, use git worktrees to |
| 78 | + inspect the relevant docs, and suggest any needed changes to avoid stale |
| 79 | + documentation. |
79 | 80 | - `CONTRIBUTING.md` states that new code should include tests and notes that |
80 | 81 | style checkers require PHP 7.4+ locally, but shipped code still has to comply |
81 | 82 | with the package's PHP `7.2` baseline. |
|
0 commit comments