Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6012

Update github action components: checkout and setup-node

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • 2
    • Not Needed
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Use Case

      As a Node.js engineer
      I want to remove deprecation warnings from our actions
      So that they continue working when support is dropped

      Our actions run with this warning:

      Annotations
      1 warning
      release_notes
      Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

      User Impact

      • None

      Dependencies

      • All our github action yml files

      Unknowns

      • Can we upgrade the gh workflows we use without issue?

      Acceptance Criteria

      Implementation Requirements

      • Ensure actions run without producing a warning about node 16

      Testing Requirements

      • None

      Documentation Requirements

      • None

      Follow Up Requirements

      • None

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: