Repository navigation
Key file: say "a secure place" instead of Teams, and use the local time zone - #10
Merged
Merged
Conversation
…me zone The key file told every researcher to keep a copy in their Teams channel files and wrote its dates in New York time. Both came from the first study. The file now names a secure place the study has approved, and writes dates in the time zone of the computer that saves it. session-client 0.1.4. The JSON data section and the format are unchanged, so files saved by 0.1.3 open as before.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The session key file told every researcher to keep a copy in their "Teams channel files" and wrote its dates in New York time. Both came from the first study and don't fit a public package.
session-clientgoes to 0.1.4. Only the human-readable header changes: the JSON data section and the file format are the same, so files saved by 0.1.3 open as before.Not in this PR:
sealed-envelope,relayanduicarry internal refactors from #9 that are not on npm. They need their own version bumps before their next release.Checked locally on Node 24:
npm test,npm run typecheck,npm run build,node scripts/check-release.mjs.